Bring your own account
The platform has no provider account of its own. That one design decision changes who owns the numbers, who holds the quota, and who appears on the invoice.
Read the guide →A timeout is not a failure
Sending is accepted asynchronously and there is no de-duplication key. Retrying a request you are unsure about sends a second message and bills for it.
Accepted is not delivered
A successful send response means the platform has taken responsibility for the message and handed it to a provider. It does not mean the message has arrived, or even that it has left. Delivery is a later, separate event that arrives as a receipt.
This matters at the moment your client gives up waiting. By the time a socket times out, the request may already have been accepted and the message already sent.
There is no retry safety net
The platform does not offer an idempotency key and does not de-duplicate requests. Sending the same request twice sends two messages and bills for both. That is a deliberate position rather than an omission: a de-duplication window would have to guess how long a caller might retry, and guessing wrong is worse than being explicit.
What to do when a request times out
- If you received a message ID, query its status or wait for the callback. Do not resend.
- If you did not, look the recipient up in the message log by time window and number before doing anything. Do not resend.
- A client-side timeout does not roll back a message the platform has already submitted, and a duplicate is billed like any other.
Designing around it on your side
The reliable pattern is to generate your own key before you call, store it with the outcome, and treat "no answer" as unknown rather than as failure. Reconcile from the message log or from `GET /open/v1/usage` instead of from your own optimistic counter.
Scope. Request handling described here is the SMS send path. Email and WhatsApp are accepted through the console today.
Keep reading
SMS segments and what you actually pay for
SMS is billed per segment, not per message. Whether your text fits in one segment depends on the character set it needs — and on the encoding you set on the connection.
Read the guide →Opt-out handling
Opt-out is two halves: the suppression record, and the check that runs before a marketing message is handed to the provider. Both run through one shared normalisation, which is the part that usually breaks.
Read the guide →Reading a delivery receipt
A receipt is a sequence of states, not a verdict. Treating an intermediate one as final is the most common way a sending dashboard ends up lying to you.
Read the guide →Pacing, quotas and why we queue
Every connection carries a send rate. The platform queues to that rate instead of firing as fast as a provider will accept, because the fastest way to get throttled is to send at the speed that causes it.
Read the guide →Routing and failover
Routes are ordered by priority and weighted within a connection. The point of the arrangement is that a provider rejecting sends degrades into slower sending, not into silence.
Read the guide →Who decides whether a message is marketing
The platform asks you to declare what kind of message you are sending instead of inferring it from the text. That one field decides whether the opt-out gate applies — and the honesty of the declaration is yours.
Read the guide →Two endpoints that look alike and are not
Delivery receipts and inbound replies are different endpoints, configured in different places in your provider’s console. Configure only the receipt URL and opt-out handling stops — silently, with no error anywhere.
Read the guide →Getting a number back
A recipient who opted out can opt back in. The platform deactivates the suppression record rather than deleting it, so the consent trail survives.
Read the guide →What happens when your callback is down
Terminal outcomes are pushed to a URL you control, with a small bounded retry. Your handler has to tolerate a repeat, and it should not expect a call for every message.
Read the guide →Which rate limit you just hit
There are two throttles in front of a send: the one your plan sets, and a much higher one at the network edge. Both answer with the same status code, so the message text is what tells them apart.
Read the guide →Who the recipient actually sees
If you do not name a sender, the platform picks one from the connection that carries the message. Naming one explicitly takes priority everywhere.
Read the guide →What the platform does not keep
Message content is not archived. What is kept is metadata — and among that metadata two fields are load-bearing, because without them a bill could not be reconciled.
Read the guide →