sinch-number-order-apilisted

Guides the multi-step Number Order workflow for purchasing phone numbers with KYC compliance via the Sinch Numbers API. Use when buying, ordering, provisioning, or activating Sinch numbers in countries that require KYC registration, regulatory compliance, or identity verification. Triggers on "number order", "KYC", "number registration", "phone number purchase", or "number provisioning".
sinch/skills · ★ 8 · AI & Automation · score 76

Install: claude install-skill sinch/skills

# Number Order API Order phone numbers with KYC compliance through a guided multi-step workflow. Required in countries where number purchases need identity verification. ## Agent Instructions This is a **sequential, fragile workflow** — steps must be followed in order. Do not combine API calls. Step 2 may be skipped if the user already has a specific E.164 number. Before starting, collect from the user: 1. **Country** — ISO 3166-1 alpha-2 region code (e.g. `AU`, `DE`, `BR`) 2. **Number type** — `MOBILE`, `LOCAL`, or `TOLL_FREE` 3. **Specific number or quantity?** — E.164 phone number, or quantity + criteria 4. **SMS or Voice?** - SMS → needs `servicePlanId` (+ `campaignId` for US 10DLC) - Voice → needs `type` (`RTC`/`EST`/`FAX`) + corresponding ID (`appId`/`trunkId`/`serviceId`) For authentication setup, see the [authentication skill](../sinch-authentication/SKILL.md). ## Workflow Execute in order. Report state to the user after each step. - [ ] **Step 1 — Lookup requirements**: `POST /v1/projects/{projectId}/numberOrders:lookupNumberRequirements` with `regionCode` + `numberType`. Save the response — it defines KYC `fields` schema and `attachments` (with `id`, `mandatory`, `allowedMimeTypes`, `allowedDocumentTypes`). Tell the user what's needed. - [ ] **Step 2 — Search available numbers** *(skip if user has a specific number)*: `GET /v1/projects/{projectId}/availableNumbers?regionCode=XX&type=YY`. Optional filters: `capabilities`, `numberPattern.pattern`, `numb