sinch-authentication

Configure Sinch API credentials and authentication across services.

9|4|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/sinch/skills --skill sinch-authentication
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sinch-authentication
Source: https://github.com/sinch/skills/tree/main/skills/sinch-authentication
Command: npx skills add https://github.com/sinch/skills --skill sinch-authentication

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes uncertainty and configuration errors when setting up authentication for Sinch APIs by identifying the correct auth model, providing concrete request examples, and offering troubleshooting for common credential and token issues.

Core Features & Use Cases

  • Auth model identification: Distinguishes project-scoped (OAuth2/Basic), application-scoped (Basic/signed), and Mailgun API key authentication and routes guidance accordingly.
  • Practical examples: Provides curl examples, recommended environment variable patterns, and SDK referral for initializing clients.
  • Troubleshooting & gotchas: Explains token expiry, region-specific API base URLs, separate credential sets (project vs application), and remediation steps for 401/403 and signature errors.
  • Use Case: Ideal for engineers onboarding a Sinch product or debugging 401/403 errors after deploying integrations.

Quick Start

Use the sinch-authentication skill to set up the correct credential type, export credentials to environment variables, and obtain an OAuth2 bearer token for API requests.

Frequently Asked Questions about sinch-authentication

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I authenticate Sinch API requests using OAuth2?

Sinch API authentication distinguishes between project-scoped OAuth2 or Basic auth and application-scoped Basic or HMAC-signed requests, routing configuration guidance based on your specific Sinch service integration scenario.

Why does my Sinch API integration return a 401 or 403 error?

Sinch API 401 or 403 errors typically result from expired OAuth2 tokens, mismatched region-specific API base URLs, or using project credentials instead of the required application-scoped keys.

How do I configure HMAC-signed requests for Sinch application APIs?

To configure HMAC-signed requests for Sinch application APIs, use your application key and secret to generate the signature, ensuring correct payload hashing to prevent signature verification failures.

Do I need different credentials for Sinch Voice, Verification, and Numbers APIs?

Yes, Sinch Voice, Verification, and Numbers APIs require different credentials, utilizing project IDs for OAuth2 tokens alongside separate application keys and secrets for HMAC-signed or Basic auth workflows.

What is the best way to manage Sinch API keys and secrets in environment variables?

The best way to manage Sinch API keys and secrets is to export project IDs, application keys, and secrets as environment variables, ensuring secure configuration and preventing hardcoded credentials in your integration code.

How do I authenticate Mailgun API key workflows with Sinch?

To authenticate Mailgun API key workflows with Sinch, configure the Mailgun API key according to the specific integration scenario, ensuring correct key usage alongside region-matching API base URLs.