API Gateways

An API Gateway is where Apiable deploys your subscriptions and syncs your APIs from. You connect the gateway that runs your APIs once under Integrations → API Gateways, then package those APIs into plans. Amazon API Gateway is the deepest, fully implemented path.

What does an API Gateway integration do?

It links Apiable to the gateway that runs your APIs. Apiable reads your APIs from the gateway so you can put them in plans, and it deploys each subscription back to the gateway so consumers can call your APIs with their credentials.

A gateway integration does two jobs:

• Sync APIs from the gateway. Apiable lists the APIs and stages on the connected gateway. You pick which ones a plan exposes.
• Deploy subscriptions to the gateway. When a consumer subscribes, Apiable provisions their access on the gateway, including the API key or OAuth client the plan calls for.

Which API gateways does Apiable support?

Apiable supports Amazon API Gateway, Azure API Management, Kong, and Apigee. You choose the type from the Select an API Gateway Type list when you add a gateway.

Gateway types your plan does not include show a Coming soon label in the picker and cannot be selected. The number of gateways your plan allows is shown on the API Gateways page.

Which gateway has the deepest support?

Amazon API Gateway. It is the fully implemented adapter in Apiable, covering API sync, subscription deployment, and the full set of per-key operations.

On Amazon API Gateway, Apiable implements API key rotation, enabling and disabling keys, validating that a plan exists on the gateway, and usage reporting per plan and per key. The other gateways connect and sync today, with some of these operations still to come.

What works on Kong, Azure, and Apigee today?

The core flow works: connect the gateway, sync its APIs, and deploy plan subscriptions to it. Some peripheral per-key operations are not yet implemented on these three gateways.

These operations are not yet implemented on Kong, Azure, or Apigee:

• Rotating a subscription's secret.
• Enabling or disabling an individual API key.
• Validating that a plan already exists on the gateway.
• Reading usage per plan or per key from the gateway.

How does a gateway connect to an Authorization Server?

Open the gateway, go to its Authorization tab, and choose the OAuth handler. Gateway-native only uses the gateway's own OAuth and is limited to Client Credentials. Authorization Server binds an external server and enables Client Credentials, Auth Code, PKCE, and JWT validation.

Picking Authorization Server reveals a picker of your connected servers. See Authorization Servers for how to connect one and how it issues tokens.

How do you connect an API gateway?

Go to Integrations → API Gateways, choose + Add Gateway, pick your gateway type, fill in its connection fields, and run Test Connection. The configure-along guide for Amazon is below.

1. Open Integrations → API Gateways.
2. Choose + Add Gateway to open Select an API Gateway Type.
3. Select your gateway type and choose to connect.
4. Fill in the connection fields for that type.
5. Click the refresh control to run Test Connection, then Save Changes.

Azure, Kong, and Apigee connect the same way from the same screen, each with its own connection fields.

Where to next