Your sign-in code
483 920
Example · valid for 5 minutesVerification codes for customers. Order alerts for your team. One key to connect it all to your application server.
500 messages for $15, paid once. No monthly subscription.
20 messages · 7 days from first connection · No card for the trial
Start with the example that fits your project. Guides and tools need no signup; real sending consumes your account credits.
Send a code, bind it to the user session and verify it on your server.
Verification code example ↗Authorized, consenting staff, a protected order link and duplicate protection.
Order alert example ↗Three templates and eight illustrative scenarios. No key, phone number or sending.
Open the free toolkit ↗Once your number is set up, your application needs only the project key. Start with a read-only request that sends nothing and spends no credits, then follow the sending and verification examples.
Agent & developer setup guide ↗curl --max-time 20 https://mz3b.com/api/v1/account/summary \
-H "Authorization: Bearer $MZ3B_API_KEY"Keep the key on your server only. Never expose it in a browser or mobile app.
A clear workflow for teams in Saudi Arabia, the UAE, Qatar, Kuwait, Bahrain and Oman, and for developers beyond the Gulf. Use international phone numbers and select the appropriate message language.
Payment and sending availability depend on the country, provider and number status. Universal coverage or delivery speed is not guaranteed.Yes. The free toolkit includes alert templates and illustrative scenarios with no signup, key or phone number. The lab does not send messages or prove a connection; live sending requires an account, a linked number and recipient consent.
No. Buy message credits once, with no automatic renewal or monthly expiry. Account, capacity and safety limits still apply.
A one-time, 7-day trial starts when your first number connects successfully, with up to 20 messages. Deleting a project or number does not restart it.
Yes, using the documentation, OpenAPI and a project key stored on your server. QR scanning, permission to send and secure key handoff still need your involvement when required.
No. Send acceptance is not delivery confirmation. Connectivity depends on WhatsApp, and this integration is not the official Meta API. Restriction bypasses and unsolicited bulk messaging are not supported.