You can use the Import Numbers API to import a non-Sinch number that you want to enable for SMS with Sinch as the Direct Connectivity Aggregator (DCA) without porting (or even partially porting) the number.
Note: Customers who are importing numbers (i.e. want to use their own NNID) will need to complete the NNID provisioning process to support proper message routing with the carriers. To learn more, refer to the article How can you provision a Network Number ID (NNID)?
Found on your Sinch Customer Dashboard. Settings > Projects.
ISO 3166-1 alpha-2 country code of the phone number. Example US, UK or SE.
The ID of the project resource. You can find your project ID on dashboard.sinch.com.
- Global APIhttps://imported.numbers.api.sinch.com/v1/projects/{projectId}/importedNumbers
curl -i -X POST \
-u '<username>:<password>' \
https://imported.numbers.api.sinch.com/v1/projects/d1923022-5199-4bb3-a513-c47b3a656bc5/importedNumbers \
-H 'Content-Type: application/json' \
-d '{
"regionCode": "US",
"smsConfiguration": {
"servicePlanId": "YOUR_service_plan_id",
"campaignId": "YOUR_campaign_id",
"migrateToSinchTmo": true
},
"phoneNumber": "+11234567890",
"displayName": "MyPhoneNumber",
"callbackUrl": "https://www.your-callback-server.com/callback"
}'OK
The ID of the project resource. You can find your project ID on dashboard.sinch.com.
ISO 3166-1 alpha-2 country code of the phone number. Example US, UK or SE.
{ "phoneNumber": "+12025550134", "projectId": "YOUR_project_id", "regionCode": "US", "displayName": "MyPhoneNumber", "smsConfiguration": { "servicePlanId": "YOUR_service_plan_id", "scheduledProvisioning": { … }, "campaignId": "YOUR_campaign_id", "migrateToSinchTmo": true }, "callbackUrl": "https://www.your-callback-server.com/callback" }