Creating an API by Importing an API from a File

Edit online

You must have the Manage APIs or Activate/deactivate APIs functional privilege assigned to perform this task.

To create an API by importing an API from a file

  1. Click APIs in the title navigation bar.
    A list of available APIs appears.
  2. Click Create API.
  3. Select Import API from file.
  4. Click Browse to select a file.
  5. Select the required file and click Open.
    The Swagger parser is a self-contained file with no external references and can be uploaded as is. If the RESTful API Modeling Language (RAML) file to be imported contains external references, the entire set of files must be uploaded as a ZIP file with a structure as referenced by the RAML file.
    Note: Importing an API fails for an invalid WSDL file.
  6. Type a name for the API name in the Name field.
    • If you provide an API name, this overwrites the API name mentioned in the uploaded file and the API is displayed with the name provided.
    • If you do not provide an API name, the API name mentioned in the uploaded file is picked up and the API is displayed with that name.
    • If you do not provide an API name and the uploaded file does not have an API name mentioned, then the API is displayed as Untitled.
    Note: Do not provide values starting with a dot (.), in any of the fields in webMethods API Gateway UI  as the external Elasticsearch does not support saving those values.
  7. Select the required type.
    The available types are OpenAPI, RAML, Swagger, WSDL, and GraphQL SDL.
  8. Provide a version for the API in the Version field.
  9. Select the team to which the API must be assigned in the Team field.
    This field appears only when the Team feature is enabled. It displays only the teams that you are a part of. If you have the User management functional privilege, all teams are displayed. You can select more than one team. To remove a team, click the delete icon next to the team to be removed.
  10. Click Create.
    An API is created with default policies.
Note:
  • To avoid encountering errors while parsing large responses from the native service, you have to change the enablesoapValidation property by commenting out the <parameter name="enableSoapValidation">true</parameter> in SAG_Install_Dir/IntegrationServer/instances/default/config/wss/axis2.xml and restart the server for the change to take effect.
  • Since the GraphQL API schema does not contain a native endpoint, you must manually update the Native endpoint URL in the API details section and the Endpoint URI in the routing policy after you create a GraphQL API.