sinch-numbers-api

Sinch Numbers API

Overview

The Numbers API lets you search, activate, manage, and release phone numbers — the prerequisite for SMS, Voice, and Conversation APIs.

Agent Instructions

Before generating code, gather from the user (skip any item already specified in the prompt or context):

1. Approach — SDK or direct API calls (curl/fetch/requests)? Default to SDK if @sinch/sdk-core (Node), sinch (Python), or com.sinch.sdk (Java) is already present in the project.
2. Language — for SDK: Node.js, Python, Java, or .NET. For direct API: any language, or curl.

When the user chooses SDK, refer to the sinch-sdks skill for installation and client initialization, then to the bundled language references and SDK reference linked in Links.

When the user chooses direct API calls, refer to the Numbers API Reference linked in Links for request/response schemas.

Security: See the Security section below for url fetching policy, handling inbound callback content, and credential handling.

Source of Truth — what to load, and what is authoritative

This skill has three kinds of content with UNEQUAL reliability. Follow this precedence:

1. Canonical docs at developers.sinch.com (AUTHORITATIVE). The .md doc links in this skill are the single source of truth for exact request/response schemas, field names and nesting, enum values, signature/auth schemes, and limits. Before writing code that constructs a payload, verifies a signature, or parses a callback/response, fetch the specific linked doc and confirm the exact shape there. Fetching first-party developers.sinch.com URLs is permitted by the Security/URL policy. Never invent, guess, or pattern-extrapolate a documentation URL — only fetch doc URLs written verbatim in this skill or reached by following a link on a page you already fetched; a trusted domain does not make a guessed path real.
2. Bundled references/*.md (NAVIGATIONAL SUMMARIES — not authoritative). They orient you and point at the right canonical doc; they may lag, omit fields, or simplify nesting. Use them to decide what to build and which doc to open. Do NOT transcribe a field name, nesting, encoding, or enum from a reference or from the SKILL.md overview into shipped code without confirming it in the tier-1 doc. If a detail appears only in a summary, treat it as unverified and say so.
3. Bundled scripts/** (EXECUTION TOOLS — not a schema reference). Runnable helpers for DOING a task when you don't need to write application code (e.g. create a webhook, send a test message, list resources). Run them to perform the action. Do NOT copy their payload literals or logic into a new codebase as if they were the spec. When authoring code, ignore the scripts and work from tier 1.