sinch porting

Manage number porting — check portability, create port-in orders, upload supporting documents, and activate ported numbers. Number porting is the process of bringing phone numbers you already own with another carrier over to Sinch so you can use them with Sinch Voice, SMS, and other products without losing the number.

Use these commands when you want to migrate existing phone numbers from a current provider to Sinch. A typical port-in flow looks like: run a portability check, update your porting contact info, create a port-in order for the numbers, upload any supporting documents the losing carrier requires, then activate the numbers once the port completes.

sinch porting
├── check          — portability checks for one or more numbers
├── config         — porting contact info, webhook URL, default port times
├── orders         — port-in order lifecycle (create, list, get, update, cancel, notes)
├── documents      — upload and download supporting documents
└── activation     — list activation groups and activate on-demand orders

All commands accept --json for machine-readable output.

Check whether one or more phone numbers are portable to Sinch.

sinch porting check <numbers...> [--json]

Example

sinch porting check +15551234567 +15557654321

Manage the porting configuration for your project — contact information, webhook URL for port status updates, and default port times.

Get the current porting configuration.

sinch porting config get [--json]

Update the porting configuration. Runs interactively by default, pre-filled with the current values. Pass --non-interactive with the flags you want to change to skip prompts.

sinch porting config update [options]

Example

sinch porting config update \
  --contact-name "Jane Doe" \
  --contact-email jane@example.com \
  --webhook-url https://example.com/porting-webhook \
  --non-interactive

Create and manage port-in orders — the request to move numbers from another carrier to Sinch.

Create a new port-in order. Runs interactively by default. For scripting, use --non-interactive with flags, or supply the full request body as a JSON file via --from-file.

sinch porting orders create [options]

Example

sinch porting orders create \
  --number +15551234567 \
  --number +15557654321 \
  --port-date 2026-05-01 \
  --port-time 10:00 \
  --port-timezone US/Eastern \
  --service-type B \
  --account-num 987654321 \
  --non-interactive

List port-in orders with optional filters.

sinch porting orders list [options]

Get the full details of a port-in order.

sinch porting orders get <orderId> [--json]

Update a pending port-in order. Interactive by default and fetches the current order so unchanged fields are preserved. Use --from-file to replace the entire request body.

sinch porting orders update <orderId> [options]

Cancel a pending port-in order. Prompts for confirmation by default.

sinch porting orders cancel <orderId> [--force] [--json]

Add a note to a port-in order. Useful for recording context or responding to carrier requests.

sinch porting orders add-note <orderId> [--note <text>] [options]

Upload and retrieve supporting documents attached to a port-in order. Losing carriers often require a Letter of Authorization (LOA) or a copy of a recent bill.

Upload a document to a port-in order. The file is base64-encoded and sent inline.

sinch porting documents upload <orderId> --file <path> [options]

Example

sinch porting documents upload ord_123 \
  --file ./loa.pdf \
  --description "Letter of Authorization"

Download a document from a port-in order. Saves the decoded file to disk by default; use --json to print metadata only without writing a file.

sinch porting documents get <orderId> <documentId> [options]

Manage activation of ported numbers. When a port-in order uses on-demand activation, numbers are ported but not yet live — they must be explicitly activated, optionally in groups.

List the available activation groups for a port-in order.

sinch porting activation list <orderId> [--json]

Activate ported numbers for an order. Without --group, activates all available groups. Prompts for confirmation by default.

sinch porting activation activate <orderId> [options]

Example

sinch porting activation activate ord_123 --group group-1 --group group-2

Porting commands use the standard OAuth2 project credentials (Project ID, Key ID, Key Secret) stored by sinch auth login. If you have not authenticated yet, run sinch auth login before using any porting command.