Everything you need to know about sending on WhatsApp with SMESS.
It's the fastest way to go live on day one — then move to your own number once it's warmed up, with no code changes.
+233000000000 (Ghana) · +44000000000 (UK) · +10000000000 (US/Canada) · +96100000000 (Lebanon) · +97100000000 (UAE) · +8600000000000 (China) — and every other country code.0240000000 (converted automatically), numbers without the + such as 233000000000, and numbers containing spaces, dashes or brackets.+233), anything starting +0, numbers shorter than 7 or longer than 15 digits, and anything containing letters.One honest note: a valid number still has to have an active WhatsApp account. If it doesn't, you'll see the reason in your dashboard (or delivery webhook) rather than a rejected send.
queue_id, and you can watch each message's final state in your portal (Queue and Messages pages). If you'd rather be told than have to look, turn on a delivery webhook:
message.status event (sent or failed, with the failure reason) the moment each message reaches its final state, so your own dashboard can show delivery problems in real time.Two separate credentials are involved: your API key authenticates messages you send, and the signing secret proves incoming webhooks really came from SMESS. Keep them distinct — then rotating one never breaks the other.
SMESS handles all the technical API routing and message delivery infrastructure. We configure your number and get you sending — but the number and its Meta compliance status remain yours.
No number ready yet? A partner business already on SMESS can sponsor your delivery with Linked Channels — see the question below.
Note: SMESS is an independent service and is not affiliated with Meta Platforms, Inc. or WhatsApp. WhatsApp is a trademark of Meta Platforms, Inc.
429 Too Many Requests error — messages are not lost, they are rejected at the API level.+1 USA, +44 UK, +233 Ghana) and messages are delivered globally. Contact us if you need support for a specific region.