sinch-porting-apilisted

# Sinch Porting API ## Overview The Porting API automates port-in operations — transferring phone numbers from another carrier into Sinch. It supports portability checks, order creation and management, document uploads, on-demand activation, and webhook notifications for status updates. Currently supports North American (US/CA) numbers only. ## Instructions Before generating code, gather from the user: 1. **Approach** — SDK or direct API calls (curl/fetch)? 2. **Use case** — Portability check, create order, track order, activate numbers? 3. **Activation mode** (only for create order) — Automatic (on `desiredPortDate`) or on-demand (`onDemandActivation: true`)? Note: The `@sinch/sdk-core` Node.js SDK does not currently have dedicated porting methods. Use direct HTTP calls for all porting operations. ## Getting Started ### Agent Credentials handling Store credentials in environment variables — never hardcode tokens, PINs, or keys in commands or source code: ```bash export SINCH_PROJECT_ID="your-project-id" export SINCH_KEY_ID="your-key-id" export SINCH_KEY_SECRET="your-key-secret" export SINCH_ACCESS_TOKEN="your-oauth-token" ``` ### Authentication Ensure that authentication headers are properly set when making API calls. The Porting API uses Bearer token authentication: ```bash -H "Authorization: Bearer $SINCH_ACCESS_TOKEN" ``` See [sinch-authentication](../sinch-authentication/SKILL.md) for full setup, most importantly how to obtain `{SINCH_ACCESS_TOKEN}` (OAuth2