Send WhatsApp login codes from your own number
A one-time code is the message a customer waits for with the app open. It has to arrive in seconds, not in the next batch. Dardasha gives login codes their own fast lane in the REST API, on a WhatsApp number you already own. This page also states the limits of that lane, because they matter.
- Sent through the REST API with your account API key
- A priority lane with a 5 to 10 second gap, ahead of campaigns
- Recognised in English and Arabic, or flagged with tier otp
- Up to 200 codes a day per line, and 6 messages a minute per line
How a code is sent
Your system calls POST /api/qr/rest/send_message with the sending line, the recipient and the text, and authenticates with the API key from your account. The API accepts the request at once and places the message in a durable queue, and a worker delivers it. Any system that can make an HTTPS request can do this: a PHP site, a Node or Python service, or a no-code automation tool.
Why a code goes before a campaign
The queue orders messages by type. Login codes are the top priority and go out after a gap of 5 to 10 seconds. Order and payment updates wait 15 to 30 seconds. Campaign messages wait 60 to 120 seconds each. When a code and a campaign message wait on the same line, the code goes first.
How Dardasha knows the message is a code
Send tier: "otp" in the request and the message always takes the priority lane. Without the flag, Dardasha reads the text: phrases such as "verification code", "your OTP" and "login code", or رمز التحقق and رمز الدخول in Arabic, also put it there. Use the flag. Wording changes over time, and a flag does not.
The limits of the lane
Every line sends at most 6 messages a minute and 100 an hour, of all types together, and at most 200 codes in a day. A code over those limits waits for the next free slot, and a code that waits is a failed login. If you expect more than a few codes a minute at peak, spread them over more than one line, or use the official API.
The rule about people who never reply
To protect the number, Dardasha sends at most three codes to a phone that has never sent a single message in, over a rolling 14-day window. The fourth is held and not delivered, although the API already accepted it. A customer who has chatted with you before is not affected. In practice this makes WhatsApp codes right for people who already talk to you, and wrong as the only route for brand new sign-ups.
The honest limit
Dardasha sends from a linked-device WhatsApp line. It is not the official WhatsApp Business API. Meta's official route for codes is the authentication template, which Meta charges per message and which has no such limits. Whichever you use, keep email or SMS as a second route, so a customer can still sign in on a bad day.
Frequently asked questions
Does Meta charge for codes sent through Dardasha?
No. Dardasha is not on the official API, so there is no Meta per-message bill. You pay the annual subscription, OMR 4.900 for Premium or OMR 14.900 for Platinum.
Can the code message be in Arabic?
Yes. The text is yours. The Arabic phrases رمز التحقق and رمز الدخول are recognised automatically, and the tier otp flag works for any language.
How do I know the code was delivered?
The API returns a queued status at once, and delivery follows after the gap. A queued status is not proof of delivery. If your system needs proof, subscribe to the message.status webhook and act on the delivered event.
Try Dardasha free for 10 days
No card required. Scan a QR code and you are live. If you stay, it is OMR 4.900 a year, billed in Omani rials.
Start free See pricing