sinch-provisioning-api

Provision WhatsApp, RCS, KakaoTalk, and webhook resources for Conversation API projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provisioning and managing messaging channel resources across multiple platforms is complex, asynchronous, and error-prone; this Skill consolidates best practices and deterministic workflows to onboard WhatsApp, RCS, KakaoTalk, Conversation channels, webhooks, templates, and multi-service bundles reliably.

Core Features & Use Cases

  • Endpoint Guidance: Maps actions to the correct project-scoped endpoint families (WhatsApp, RCS, KakaoTalk, Conversation, Webhooks, Bundles) to avoid misrouted requests.
  • Safe Defaults & Error Handling: Recommends webhook uniqueness, trigger strategies, retry/backoff for 429/5xx, and uses PAPI Error resolution fields for 4xx corrections.
  • Async Operation Support: Describes using provisioning webhooks or polling status endpoints to verify asynchronous transitions for senders, templates, accounts, and bundles.
  • Use Case: Onboard a WhatsApp sender, submit templates, register a provisioning webhook to receive completion events, and verify resulting resource IDs and states.

Quick Start

Provision a WhatsApp sender for project PROJECT_ID, register a unique provisioning webhook callback URL using OAuth2 bearer authentication, and return the new sender ID and final verification state.

Frequently Asked Questions about sinch-provisioning-api

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

FAQPage Schema
How do I automate WhatsApp sender registration and template provisioning for a Conversation API project?

To automate WhatsApp sender registration and template provisioning, you map actions to project-scoped endpoints under /v1/projects/{projectId}/, submit your templates, and verify asynchronous completion states via polling or provisioning webhooks.

What is the best way to handle asynchronous states when provisioning RCS or KakaoTalk messaging channels?

Handling asynchronous states for RCS or KakaoTalk channels requires registering a unique provisioning webhook callback URL to receive completion events, or alternatively polling status endpoints to verify the final resource states.

How does webhook uniqueness and retry backoff work when managing messaging channel resources?

Webhook uniqueness prevents duplicate callback triggers, while retry backoff manages rate limits and transient failures by exponentially delaying subsequent requests for 429 or 5xx errors during channel resource management.

Does the Sinch Conversation API support OAuth2 bearer tokens for provisioning bundles and templates?

Yes, the Sinch Conversation API supports OAuth2 bearer tokens or Basic auth for authenticating provisioning requests, ensuring secure management of bundles, templates, and channel resources across your projects.

Why does PAPI-style error handling matter when orchestrating multi-service bundles for messaging platforms?

PAPI-style error handling matters because it provides specific error resolution fields for 4xx corrections, enabling deterministic workflows and reliable recovery when orchestrating complex multi-service bundles across messaging platforms.