Integrations
Integrations
Integrations connect Apiable to the systems that run your APIs and sign in your users: identity providers, authorization servers, API gateways, and payment providers.
Integrations connect Apiable to the systems that run your APIs and sign in your users. You connect each one once under Integrations, then reuse it across your account.
What can you integrate with Apiable?
Two integration types are documented here: identity providers, which sign developers in to your API Portal, and authorization servers, which issue the OAuth2 tokens your gateway validates. Apiable also connects to API gateways and payment providers.
| Integration | What it does |
|---|---|
| Identity Providers | Sign developers in to your API Portal, with Microsoft Entra ID, Amazon Cognito, or OpenID Connect. |
| Authorization Servers | Issue the OAuth2 tokens your gateway validates, with Keycloak or Auth0. |
| API Gateways | Connect the gateway that runs your APIs, with Amazon, Azure, Kong, or Apigee. |
| Payment Providers | Take payment for paid plans through Stripe. See Monetization. |
How do identity providers and authorization servers differ?
An identity provider signs human users in to your API Portal. An authorization server issues the OAuth2 tokens your gateway validates for machine-to-machine API calls. They solve different problems and are set up separately in Apiable.
Where to start
Identity Providers
Connect Microsoft Entra ID, Amazon Cognito, or OpenID Connect so developers can sign in to your API Portal.
Authorization Servers
Connect Keycloak or Auth0 to issue the scoped OAuth2 tokens your gateway validates.
API Gateways
Connect the gateway that runs your APIs, with Amazon, Azure, Kong, or Apigee.