← ClaudeAtlas

sinch-verification-apilisted

Verify phone numbers via SMS, Flashcall, Phone Call, Data (seamless carrier-level), or WhatsApp with Sinch Verification API. Use when implementing user phone verification, OTP, two-factor authentication, or number ownership confirmation flows.
sinch/skills · ★ 8 · AI & Automation · score 76
Install: claude install-skill sinch/skills
# Sinch Verification API ## Overview The Sinch Verification API verifies phone numbers through SMS OTP, Flashcall (missed call CLI), Phone Call (spoken OTP), Data (carrier-level), and WhatsApp OTP. Used for registration, 2FA, and number ownership confirmation. **Base URL:** `https://verification.api.sinch.com` **URL path prefix:** `/verification/v1/` **Auth:** Application Key + Secret (NOT project-level OAuth2 — see [Authentication Guide](https://developers.sinch.com/docs/verification/api-reference/authentication.md)) ## Agent Instructions Before generating code, you **MUST** ask the user: 1. **Which verification method?** — `sms`, `flashcall`, `callout`, `seamless`, or `whatsapp` 2. **SDK or direct HTTP?** — If SDK, which language? Do not assume defaults or skip these questions. Wait for answers before generating code. For SDK syntax and setup, see [sinch-sdks](../sinch-sdks/SKILL.md). For direct HTTP, use the [API Reference (Markdown)](https://developers.sinch.com/docs/verification/api-reference/verification.md) for request/response schemas. ## Getting Started ### Agent Credentials handling Store credentials in environment variables — never hardcode application keys or secrets in commands or source code: ```bash export SINCH_APPLICATION_KEY="your-application-key" export SINCH_APPLICATION_SECRET="your-application-secret" ``` ### Authentication Ensure that authentication headers are properly set when making API calls. The Verification API uses **Application