Sinch · OAuth Scopes

Sinch OAuth Scopes

OAuth 2.0 derived

Sinch publishes 3 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Sinch API on a user’s behalf.

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.

CommunicationsMessagingSMSVoiceVerificationCPaaSTelecommunicationsWhatsApp

Scopes: 3 Flows: clientCredentials Method: derived

OAuth endpoints

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

Flows
clientCredentials

Scopes (3)

Scope	Description	Flows
-	-	clientCredentials
read	read	clientCredentials
write	write	clientCredentials

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-10-08'
method: derived
source: openapi/original-sinch-conversation-openapi.yml, openapi/original-sinch-elastic-sip-trunking-openapi.yml,
  openapi/original-sinch-fax-openapi.yml, openapi/original-sinch-numbers-openapi.yml, openapi/original-sinch-provisioning-openapi.yml,
  openapi/original-sinch-registration-openapi.yml, openapi/sinch-10dlc-registration-api-openapi.yml,
  openapi/sinch-access-control-lists-api-openapi.yml, openapi/sinch-access-keys-api-openapi.yml,
  openapi/sinch-access-keys-legacy-api-openapi.yml, openapi/sinch-active-numbers-api-openapi.yml,
  openapi/sinch-apps-api-openapi.yml, openapi/sinch-available-numbers-api-openapi.yml, openapi/sinch-available-regions-api-openapi.yml,
  openapi/sinch-brands-api-openapi.yml, openapi/sinch-capability-api-openapi.yml, openapi/sinch-compliance-brands-api-openapi.yml,
  openapi/sinch-contacts-api-openapi.yml, openapi/sinch-conversation-api-openapi.yml, openapi/sinch-conversations-api-openapi.yml,
  openapi/sinch-elastic-sip-trunking-api-openapi.yml, openapi/sinch-events-api-openapi.yml,
  openapi/sinch-fax-api-openapi.yml, openapi/sinch-fax-to-email-api-openapi.yml, openapi/sinch-faxes-api-openapi.yml,
  openapi/sinch-imported-numbers-hosting-orders-api-openapi.yml, openapi/sinch-kakaotalk-senders-api-openapi.yml,
  openapi/sinch-line-senders-api-openapi.yml, openapi/sinch-market-requirements-api-openapi.yml,
  openapi/sinch-messages-api-openapi.yml, openapi/sinch-number-lookup-api-openapi.yml, openapi/sinch-numbers-api-openapi.yml,
  openapi/sinch-phone-numbers-api-openapi.yml, openapi/sinch-porting-api-openapi.yml, openapi/sinch-projects-api-openapi.yml,
  openapi/sinch-provisioning-api-openapi.yml, openapi/sinch-rcs-senders-api-openapi.yml, openapi/sinch-registrations-api-openapi.yml,
  openapi/sinch-sip-endpoints-api-openapi.yml, openapi/sinch-sip-trunks-api-openapi.yml, openapi/sinch-subprojects-api-openapi.yml,
  openapi/sinch-telegram-senders-api-openapi.yml, openapi/sinch-template-management-api-openapi.yml,
  openapi/sinch-transcoding-api-openapi.yml, openapi/sinch-us-shortcode-campaigns-api-openapi.yml,
  openapi/sinch-voice-api-v2-openapi.yml, openapi/sinch-webhooks-api-openapi.yml
schemes:
- name: OAuth2
  source: openapi/sinch-10dlc-registration-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: This is the recommended way to access our APIs in production.
- name: OAuth2
  source: openapi/sinch-access-keys-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: The user name and password are your client_id and key_secret from the [Access
    Keys sections](https://dashboard.sinch.com/settings/access-keys)
- name: OAuth2
  source: openapi/sinch-access-keys-legacy-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: The user name and password are your client_id and key_secret from the [Access
    Keys sections](https://dashboard.sinch.com/settings/access-keys)
- name: OAuth2
  source: openapi/sinch-brands-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: The username and password are your Key ID and Key Secret from the Access keys
    section in the Sinch Customer Dashboard. Exchange these for a bearer token (access token).
- name: OAuth2
  source: openapi/sinch-compliance-brands-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: The username and password are your Key ID and Key Secret from the Access keys
    section in the Sinch Customer Dashboard. Exchange these for a bearer token (access token).
- name: oAuth2
  source: openapi/sinch-conversation-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: The user name and password are your client_id and key_secret from the [Access
    keys sections](https://dashboard.sinch.com/settings/access-keys)
- name: OAuth2.0
  source: openapi/sinch-elastic-sip-trunking-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: To use OAuth 2.0 authentication, use your Access Key ID and Access Key Secret
    to obtain your bearer token. For detailed instructions on how to do this, see the [OAuth
    Authentication](https://developers.sinch.com/docs/est/api-reference/est#oauth) section.
- name: OAuth2
  source: openapi/sinch-fax-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: The user name and password is your key id and key secret from the [Access keys
    sections](https://dashboard.sinch.com/settings/access-keys)
- name: OAuth2.0
  source: openapi/sinch-imported-numbers-hosting-orders-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: The username and password are your Key ID and Key Secret from the [Access keys
    section](https://dashboard.sinch.com/settings/access-keys) in the Sinch Customer Dashboard.
    Exchange these for a bearer token (access token). Learn how [here](https://developers.sinch.com/docs/numbers/api-reference/authentication/oauth).
- name: OAuth2
  source: openapi/sinch-number-lookup-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
- name: OAuth2.0
  source: openapi/sinch-numbers-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: The username and password are your Key ID and Key Secret from the [Access keys
    section](https://dashboard.sinch.com/settings/access-keys) in the Sinch Customer Dashboard.
    Exchange these for a bearer token (access token). Learn how [here](https://developers.sinch.com/docs/numbers/api-reference/authentication/oauth).
- name: bearerAuth
  source: openapi/sinch-porting-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: The username and password are your Key ID and Key Secret from the [Sinch Build
    Dashboard](https://dashboard.sinch.com/settings/access-keys). Exchange these for a bearer
    token (access token). Learn how [here](https://developers.sinch.com/docs/numbers/api-reference/authentication/oauth).
- name: OAuth2Production
  source: openapi/sinch-provisioning-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth2 authorization for production
- name: OAuth2.0
  source: openapi/sinch-subprojects-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: The username and password are your Key ID and Key Secret from the [Access keys
    section](https://dashboard.sinch.com/settings/access-keys) in the Sinch Customer Dashboard.
    Exchange these for a bearer token (access token).
- name: oAuth2
  source: openapi/sinch-template-management-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: The user name and password are your client_id and key_secret from the [Access
    keys sections](https://dashboard.sinch.com/settings/access-keys)
- name: OAuth2
  source: openapi/sinch-us-shortcode-campaigns-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: The username and password are your Key ID and Key Secret from the Access keys
    section in the Sinch Customer Dashboard. Exchange these for a bearer token (access token).
- name: SinchOAuth2
  source: openapi/sinch-voice-api-v2-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: |-
    OAuth 2.0 **Client Credentials** grant (recommended for production).

    Exchange the **Access Key ID** (`client_id`) and **Access Key Secret**
    (`client_secret`) for a short-lived Bearer token.

    Tokens typically expire after **3600 seconds**. When the token expires,
    request a new one using the same `tokenUrl`. There is no separate
    refresh token in the client credentials flow — simply re-authenticate.

    Access keys are managed in the Dashboard: https://dashboard.sinch.com/settings/access-keys
- name: oAuth2
  source: openapi/original-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/original-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/original-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/original-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/original-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/original-sinch-registration-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
- name: oAuth2
  source: openapi/sinch-access-control-lists-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
- name: oAuth2
  source: openapi/sinch-active-numbers-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
- name: oAuth2
  source: openapi/sinch-apps-api-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-available-numbers-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
- name: oAuth2
  source: openapi/sinch-available-regions-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
- name: oAuth2
  source: openapi/sinch-capability-api-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-contacts-api-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-conversations-api-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-events-api-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-fax-to-email-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
- name: oAuth2
  source: openapi/sinch-faxes-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
- name: oAuth2
  source: openapi/sinch-kakaotalk-senders-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
- name: oAuth2
  source: openapi/sinch-line-senders-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
- name: oAuth2
  source: openapi/sinch-market-requirements-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
- name: oAuth2
  source: openapi/sinch-messages-api-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-phone-numbers-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
- name: oAuth2
  source: openapi/sinch-projects-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
- name: oAuth2
  source: openapi/sinch-rcs-senders-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
- name: oAuth2
  source: openapi/sinch-registrations-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
- name: oAuth2
  source: openapi/sinch-sip-endpoints-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
- name: oAuth2
  source: openapi/sinch-sip-trunks-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
- name: oAuth2
  source: openapi/sinch-telegram-senders-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinch.com/oauth2/token
  description: OAuth 2.0 client credentials flow.
- name: oAuth2
  source: openapi/sinch-transcoding-api-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-webhooks-api-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.
scopes:
- scope: '-'
  description: '-'
  flows:
  - clientCredentials
  sources:
  - openapi/sinch-provisioning-api-openapi.yml
- scope: read
  description: read
  flows:
  - clientCredentials
  sources:
  - openapi/sinch-brands-api-openapi.yml
  - openapi/sinch-compliance-brands-api-openapi.yml
  - openapi/sinch-us-shortcode-campaigns-api-openapi.yml
- scope: write
  description: write
  flows:
  - clientCredentials
  sources:
  - openapi/sinch-brands-api-openapi.yml
  - openapi/sinch-compliance-brands-api-openapi.yml
  - openapi/sinch-us-shortcode-campaigns-api-openapi.yml

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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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