Overview
What Sinch is
Sinch is a global communications platform that provides an SMS API for sending text messages worldwide through its direct carrier network.
Courier sits in front of it as one API, so you keep Sinch for SMS and add push, an in-app inbox, design, and journeys on top.
You need a Courier account and your own Sinch account (Service Plan ID, API token, and a from number).
Why Courier
What you get with Sinch + Courier
Add push in the same send
Reach mobile and web with push alongside SMS from one notification, no new integration in your code.
Add an in-app inbox for web and mobile
Give your app an in-product notification center (SDKs for web, React, iOS, Android, Flutter, React Native), so users see more than just texts.
Automate multi-step flows
Trigger reminders, verification, and lifecycle sequences with delays and branching, all delivered through Sinch.
Write once, edit without code
Compose and localize SMS copy in Courier's editor. Product and support change messaging without a deploy.
Send to lists and audiences
Broadcast a one-off or recurring text to an entire list through Sinch, alongside your transactional messages.
Localize a message in seconds
Pick a language and let Courier translate your message with AI, then tweak any string.
Use cases
What teams build with it
Setup
Connect it in minutes
An admin adds Sinch once on the Integrations page in Courier. Once connected, anyone on your team can send SMS through Sinch and add push or an in-app inbox whenever they need them.
FAQ
Frequently asked questions
Can I use Sinch with Courier?
Yes. Sinch is a supported SMS provider in Courier. Connect it and Courier routes SMS through Sinch while you send with one Send API and orchestrate delivery across your other channels.
Do I still need my own Sinch account?
Yes. Courier does not resell Sinch. You keep your own Sinch account and Service Plan, and Courier authenticates with your credentials so Sinch still delivers the SMS.
What do I need to connect Sinch to Courier?
Three things: your Sinch Service Plan ID, API token, and a From number, all entered on the Sinch integration page in Courier. Courier then sends SMS through your Sinch account.
Can I override Sinch credentials per message in Courier?
Yes. Beyond the account-level setup, you can override apiToken, servicePlanId, url, and from per message via message.providers.sinch.override, which is useful for routing through a different Sinch Service Plan or sender.
What sets the SMS sender number for Sinch in Courier?
The from field. It holds the SMS sender you have provisioned in Sinch, configured on the integration and overridable per message. Sinch delivers using that number as the sender.
What phone number format does Sinch require in Courier?
E.164. Store each recipient's SMS number as phone_number on their Courier profile, such as +12025550156. Courier passes that value to Sinch as the destination for delivery.
Is Courier a replacement for Sinch?
No. Sinch still delivers the SMS. Courier sits in front as one Send API, adding Design Studio and Journeys, plus push, email, and Courier Inbox across channels.
More
