sinch-provisioning-apilisted

Provisions and manages channel resources for Conversation API projects, including WhatsApp accounts/senders/templates, RCS senders, KakaoTalk senders/templates, webhooks, and bundles. Use when the user asks to onboard channels, configure provisioning webhooks, manage templates, orchestrate multi-service bundles, or automate channel setup.
sinch/skills · ★ 8 · AI & Automation · score 78

Install: claude install-skill sinch/skills

# Sinch Provisioning API ## Overview Use this skill for Conversation API channel provisioning. Validated against Provisioning API v1.2.36. Prefer deterministic flows: confirm context, choose endpoint family, execute minimal calls, verify state. ## Agent Workflow (Default) Use this sequence unless the user requests otherwise. 1. Confirm scope and identifiers - Confirm `projectId` - Confirm microservice scope — each is a separate REST service: WhatsApp, RCS, KakaoTalk, Conversation, Webhooks, or Bundles 2. Choose the endpoint family first - WhatsApp account/senders/templates/flows/solutions: `/v1/projects/{projectId}/whatsapp/...` - RCS: `/v1/projects/{projectId}/rcs/...` - KakaoTalk: `/v1/projects/{projectId}/kakaotalk/...` - Conversation (channel info): `/v1/projects/{projectId}/conversation/...` - Webhooks: `/v1/projects/{projectId}/webhooks...` - Bundles: `/v1/projects/{projectId}/bundles...` 3. Apply safe defaults - Webhook `target` must be unique per project - Use `ALL` for webhook triggers when broad coverage is needed - WhatsApp template language delete: `deleteSubmitted` defaults to `false` 4. Verify async operations - Some operations are asynchronous — register a provisioning webhook to receive completion notifications - Webhook payloads contain the full JSON response as payload - Alternatively, poll status endpoints for state changes - For bundles, subscribe to `BUNDLE_DONE` 5. Handle failures predictably - All endpoints return a PAPI Error (Provisioning API