Creating APIs
Create an API by using a file, URL, or by providing the source content.
Before you begin
Make sure that you have the file, URL, or the specification for creating the API.
About this task
webMethods Developer Portal supports the publishing of OData APIs from provider applications such as API Gateway. However, you cannot create OData APIs in webMethods Developer Portal by providing a specification.
In this example, you create an API Petstore using the https://petstore.swagger.io/v2/swagger.json URL. The API is assigned to the provider, Provider1, and the community, Mobile_app_developer.
Procedure
- Click the menu options icon
from the title bar and click Manage assets and
click APIs. The list of APIs appears. - Click Create API.
- Provide Petstore in the Name field.
- Select Swagger from the Type list.
- Select Provider1 in the Provider
field. If you are creating the API for a third-party API gateway, make sure that the gateway is registered for the value to be available in the Provider field.
- Select Mobile_app_developer from the
Community field. If you select a private community remove the Public community which is selected by default. Hence, the API is available only for the selected private community members.
- Select a URL from the Import with section and provide https://petstore.swagger.io/v2/swagger.json in the field.
- Click Create. The API is created. You can view the API from the API gallery page and the Manage APIs page.
What to do next
- You can create other types of APIs by selecting a
corresponding option from the Type list.
- Open API . To create a REST API by using an Open API specification.
- RAML. To create a REST API by using a RAML specification.
- WSDL. To create a SOAP API by using a WSDL specification.
- You can use the one of the following inputs to create
an API from the Import with section:
- File. To create API from a file. Click Browse and select a file.
- Content. To create API from the specified content. Provide the parser content using which the API must be created. Make sure that the content does not have references to external files.
- If the API lifecyle feature is enabled, then the newly created API is kept in the Draft state. For information about the API lifecycle, see Managing lifecycle of APIs and packages.
- Move the API to the Live state to make it available for consumers. For information on moving APIs to the Live state, see Changing the state of an API to expose it to consumers.
- Configure a rate limit for your APIs. For details steps, see Configuring rate limit for APIs.