Integrations

Link an API integration: choose user session, legacy API key, OAuth2 machine client or outbound webhook.

Before you start

  • Use the correct company and an active account with permission for this workflow.

Where to go

Workspace → Integrations

Audience

Business owners and company owners and active company admins.

Permissions

  • Only business owners and authorized company owners and active company admins may manage this view.

Actions

Review OAuth2 clients
Use Review OAuth2 clients to support discover supported integration workflows and credential status.
Review legacy API credentials
Use Review legacy API credentials to support discover supported integration workflows and credential status.

Statuses

Supported OAuth2 workflows
The record is currently supported oauth2 workflows.
Legacy API-key operations unavailable
The record is currently legacy api-key operations unavailable.

Workflow

  1. Use the signed-in user session for permitted workspace actions; keep session tokens in the existing application.
  2. API Keys supports legacy management and revocation only; no working operational consumer is verified.
  3. Choose OAuth2 Clients for vendor server-to-server work, with the smallest assigned scope. External buyer API Access uses a separate account and scope vocabulary.
  4. Choose Webhooks for an outbound test event sent to your saved public HTTPS receiver. Reading these guides creates no credential and sends no event.

Expected outcome

Read the current saved state in the workspace after the permitted action; Help does not perform or verify the action.

Troubleshooting

A credential exists but the integration is unverified
Credential creation does not verify a working integration. Follow the supported OAuth2 guide; retired API-key endpoints remain unavailable.