Create APIs

AMPLIFY API Management provides two ways to create new APIs.

Create APIs using API Builder

API Builder is the primary option for creating new APIs.

In API Builder, APIs are created as projects, standard Node.js applications running in the Arrow Cloud environment. You create a project, add API end-points (API Builder APIs) to define ways how client applications can access your API, or other components, such as models. Once your API is ready, API Builder generates a Swagger 2.0 definition for the API (see API Builder Console documentation). You can then import the Swagger definition to API Manager and register the API.

API Builder comes with prebuilt connectors for different services, such as Salesforce, Azure, MS SQL, MySQL, MongoDB, orSwagger, making integration with cloud applications and services easy. In addition you can create custom connectors for any data source, and reuse the connectors as needed in your APIs. For easy integration with mobile applications, you can optimize the payload size and data format for your APIs.

For a walk-through of the basics of API creation, see API Builder Getting Started Guide.

Create APIs using API Gateway

Sometimes it may be better to create new APIs using API Gateway, especially when integrating with back-end services. For example, you might need to bridge an API Key or OAuth identity of the API in API Manager to an identity used by back-end services, like Kerberos. Or the back-end service you are integrating with might require JSON/XML data transformation for request/response messages.

You can create new APIs in Policy Studio using the REST API development wizard. The REST APIs can be based on existing back-end REST or non-REST APIs, but you must specify a custom routing policy for REST API methods. The policies for request and response processing are optional, and you can specify them as required. When your API is ready, you can register it in API Manager.

For more details on creating new APIs in Policy Studio, see Develop REST APIs in Policy Studio in the API Gateway Policy Developer Guide.

Related Links