Skip to content

Integrations

Integrations

Every provider Alter connects to, with how to connect it and how to call it

Each provider in the sidebar has one entry with everything about it in one place. A few providers offer more than one integration (for example a separate API-user or management API); those are listed side by side under the provider’s name.

  • Connect with OAuth: the provider authorizes an end user’s account, and Alter stores the resulting token. See Connecting with OAuth.
  • Connect with an API key: the application’s operator, or an end user in a Connect session, stores the provider’s API key or other credential, and Alter injects it into each call. See Connecting with an API key.
  • SDK: for some providers, a typed package (for example @alter-ai/deel and alter-sdk-deel) with a method for every operation in the provider’s API, and an API reference of each operation’s fields. See Provider SDKs.

A provider shows the parts it supports. Some connect only one way, and only some have a typed SDK. Without one, call the provider’s API through the core Python or TypeScript SDK, which works with every provider.

Every call made through Alter, with either connection type and through any SDK, goes through the same controls: the connection’s authorization, policy rules, approvals, quotas, revocation and audit.

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.