Sinch · OAuth Scopes

Sinch OAuth Scopes

OAuth 2.0 derived

Sinch uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

Tokens are issued from https://auth.sinch.com/oauth2/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CommunicationsMessagingSMSVoiceVerificationCPaaS
Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://auth.sinch.com/oauth2/token
Flows
clientCredentials

Scopes (0)

Sinch implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

Sinch OAuth 2.0 uses the client_credentials flow with project access keys (key ID and secret) and does not publish or use OAuth scopes (https://developers.sinch.com/docs/numbers/api-reference/authentication/oauth).

Source

OAuth Scopes

Raw ↑
generated: '2026-07-11'
method: derived
docs: https://developers.sinch.com/docs/numbers/api-reference/authentication/oauth
note: Sinch OAuth 2.0 uses the client_credentials flow with project access keys (key
  ID and secret) and does not publish or use OAuth scopes (https://developers.sinch.com/docs/numbers/api-reference/authentication/oauth).
source: openapi/sinch-conversation-openapi.yml, openapi/sinch-elastic-sip-trunking-openapi.yml,
  openapi/sinch-fax-openapi.yml, openapi/sinch-numbers-openapi.yml, openapi/sinch-provisioning-openapi.yml,
  openapi/sinch-registration-openapi.yml
schemes:
- name: oAuth2
  source: openapi/sinch-conversation-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow using project key ID and secret.
- name: oAuth2
  source: openapi/sinch-elastic-sip-trunking-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
- name: oAuth2
  source: openapi/sinch-fax-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
- name: oAuth2
  source: openapi/sinch-numbers-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
- name: oAuth2
  source: openapi/sinch-provisioning-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
- name: oAuth2
  source: openapi/sinch-registration-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
scopes: []

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This scope set
curl "https://apis.io/api/v1/scopes/sinch-scopes"
All oauth scopes
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.