sinch-porting-api

Automate port-in order creation and phone number transfers into Sinch via REST API.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a clear, repeatable workflow to port phone numbers from other carriers into Sinch, reducing manual coordination with losing carriers and preventing common validation rejections.

Core Features & Use Cases

  • Portability checks before ordering to avoid failed submissions.
  • Create and manage port-in orders, including full-object updates for pending orders and cancellation flows.
  • Document uploads and on-demand activation with group-based activation once FOC is reached.
  • Order tracking and webhooks to receive real-time status updates and handle lifecycle events.
  • Use Case: Port 100 US business numbers by running portability checks, submitting a port-in order with LOA attachments, and activating groups on the FOC date.

Quick Start

Check portability for +15551234567 and create a port-in order with onDemandActivation set to true.

Frequently Asked Questions about sinch-porting-api

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

FAQPage Schema
How do I port phone numbers into Sinch using the porting API?

Port phone numbers into Sinch by automating port-in order creation, applying to North American US/CA numbers using REST API calls with E.164-formatted phone numbers. The process includes portability checks, order tracking, document uploads, and on-demand activation workflows.

What is a portability check and when do I need it for a port-in order?

A portability check verifies whether North American phone numbers can be transferred to Sinch before submitting an order. You need it to prevent failed submissions and avoid common validation rejections from losing carriers during the port-in process.

How do I handle on-demand activation for ported numbers once FOC is reached?

Handle on-demand activation for ported numbers by using group-based activation endpoints once the FOC date is reached. Set onDemandActivation to true during port-in order creation to trigger this workflow automatically.

Can I update a pending port-in order after submitting it?

Yes, you can update pending port-in orders by performing full-order PUT updates via REST API calls. This allows you to modify the entire order object, manage document uploads like LOA attachments, or initiate cancellation flows while the order is still pending.

How do I track the status of my Sinch port-in orders?

Track Sinch port-in order status by configuring webhooks to receive real-time lifecycle event updates. This webhook configuration lets you monitor order progress and handle status changes as numbers transfer from the losing carrier.