Sender numbers and how they are chosen
Most senders never specify a from address, and that is usually correct. Here is when to override it.
Read this article →Connect your own provider account
Bring-your-own-account keeps the agreement, the sender reputation and the invoice with your CPaaS provider. Here is how to connect one, and what changes once you do.
What "your own account" means
You connect an account you already hold. The platform stores the credentials you paste, routes through your account, and never becomes the party your provider invoices.
This is the difference that matters commercially: the pricing you negotiated, the sender numbers you already registered, and the delivery reputation you have built all stay where they are.
Scope. Six providers can be connected today. Chinese and additional international providers are in development; they appear in the console as coming soon and cannot be connected yet.
Which credentials each provider expects
Every provider asks for a different pair. The console labels every field and refuses to save until all required fields are present.
| Provider | Credentials |
|---|---|
| Twilio | Account SID + Auth Token (account-level, not an API key pair) |
| Vonage | API key + API secret |
| Infobip | API key + base URL |
| MessageBird | Access key |
| Plivo | Auth ID + Auth token |
| AWS End User Messaging | Access key + secret + region |
Connect a provider
Add a connection
Channels → Add connection, then choose the provider type.
Paste the credentials
Use the field labels above as a checklist. Nothing is sent anywhere until you save.
Save and confirm the status
The connection appears in the list. Its status becomes ACTIVE once the platform has accepted the credentials.
Note. Credentials are encrypted before they are stored and are never shown in full again. Copy them from your provider dashboard if you need to check them later.
What ACTIVE does and does not mean
ACTIVE means the credentials validated. It does not promise that a given sender number is accepted by the provider, or that a destination country is reachable on that route.
Those refusals surface per message, as a failed status with an error code — see "Messages that fail with an error code".
Editing and removing a connection
A masked credential field is not a value you have to retype. Editing any field on the form re-encrypts only what you actually changed, so the stored secret survives an unrelated edit.
Removing a connection takes its sender numbers out of the rotation. An API key bound to it will have one fewer channel to send over — and a key left with no bound channel is rejected at send time.
Keep reading
Route across providers with priority and weight
Bind a key to more than one provider and the platform becomes the routing layer — balancing load when all is well, failing over when it is not.
Read this article →Verify a connection before you rely on it
The built-in check only validates the fields you typed. Here is the test that actually proves a connection works.
Read this article →