Getting started with SMS

Provisioning API allows you to create and manage SMS Applications (SMS Apps). An SMS App represents an SMS sender configuration within a specific region. To send SMS messages through Sinch, the SMS App must be linked to a Conversation Application, which acts as the unified messaging layer.

This guide covers:

• Creating an SMS App using the Provisioning API
• Connecting an SMS App to a Conversation Application
• Managing SMS Apps: listing, retrieving, updating, and deleting

To use the SMS provisioning endpoints, you need:

• A Sinch account: dashboard.sinch.com
• Project credentials (Access Key and Access Secret): Access Keys
• Project ID

The SMS App requires a name and a region. Available regions are:

Every SMS App must be linked to a Conversation Application before it can send messages. There are two approaches:

• Using the SMS endpoint — create the SMS App with convApiApp: true or convApiAppId to link at creation time, or create as a standalone SMS App and connect to an existing Conversation Application afterwards.
• Using the Bundles endpoint — create the SMS App and Conversation Application together in a single atomic request.

See the SMS Apps guide for full details, code samples, and the connect endpoint for post-creation linking. See the Bundles guide for the Bundles approach.

For full CRUD operations and code samples, see the SMS Apps guide.