sinch.com

5 integrations · REST · CLI

Sinch exposes multiple authenticated developer surfaces including HTTP APIs (e.g. Numbers, Conversation, Subprojects, Access Keys Management) and a CLI, using either project access keys (Key ID + Key Secret) via Basic auth, OAuth 2.0 client-credentials bearer tokens derived from those keys, and for SMS/Voice some product-specific credentials like SMS API tokens and Voice app key/secret.

discovered 2mo ago

REST · OpenAPI4

Sinch Numbers APIdiscoveredrest
Sinch Subprojects APIdiscoveredrest
Sinch Access Keys Management APIdiscoveredrest
Sinch Conversation APIdiscoveredrest

CLI1

Sinch CLIdiscoveredsinch

Credentials

Sinch access key (Key ID + Key Secret for a project)compoundGet key ↗

In the Sinch Build Dashboard, open Access keys and click Create Access Key. Save the Key ID, Key Secret, and associated project ID; the Key Secret is only shown at creation time. These credentials can be used directly with HTTP Basic auth for testing, or exchanged at `https://auth.sinch.com/oauth2/token` using the client_credentials grant to obtain a short-lived bearer token.

Sinch OAuth 2.0 access tokenoauth2_cc$ sinch auth login

Acquired by the CLI — running sinch auth login opens the auth flow and stores the credential.

conventions · 0/8 published

integrations.json✗/.well-known/integrations.json
llms.txt✗/llms.txt
API catalog✗/.well-known/api-catalog
OpenAPI document✗/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json
MCP server card✗/.well-known/mcp/server-card.json
OAuth protected resource✗/.well-known/oauth-protected-resource
Agent card✗/.well-known/agent-card.json
Agent skills✗/.well-known/agent-skills/index.json

Publish these signals → /publishing