Send and check
Six digits, good for ten minutes, five tries. A right code is accepted once. The same number again within a minute is the same request, so a double tap costs nothing.
Meetowt Verify New
Your app asks Meetowt to send a person a six-digit code on WhatsApp, then asks whether the code they typed is right. Two calls, from your own WhatsApp Business number, so the person sees your name and not ours.
No WhatsApp number is needed to start: a test key never reaches Meta and never costs anything.
With a work email, at my.meetowt.com/developers/signup. No workspace, no mail, no staff: an account for codes only. A company that already has a Meetowt workspace finds the same screen in Admin, then Verify.
On the Verify screen. It is shown once, and Meetowt keeps only a fingerprint of it.
From your own program, or from the screen itself, which shows the exact request and answer. A test code is always 000000 and moves through sent, delivered and read on its own.
Paste your WhatsApp Business account id, phone number id, a permanent access token and the app secret. Meetowt checks them with Meta, makes the code message in English, Arabic and French, and you make a live key.
Every one of these is in the API guide, with samples in curl, Node.js, Python, PHP, C# and Java.
Six digits, good for ten minutes, five tries. A right code is accepted once. The same number again within a minute is the same request, so a double tap costs nothing.
A key of its own kind that never reaches Meta: the code is always 000000, and a test key reads only test codes, a live key only real ones.
For a software house: each of your own customers gets its own keys, daily limit, countries and delivery address, and if it wants its own WhatsApp number. One client's key can never read another's codes.
Send your own approved utility templates, such as an order update, a reminder or a receipt, through the same queue and log. Marketing templates are never sent. Alerts are not priced yet and are free during early access.
Whether a number is valid, its country and whether it is a mobile or a landline, worked out on our own server from published numbering tables. It cannot tell whether the number has WhatsApp or the line is switched on.
Sent, delivered, read, failed, checked right and expired, posted to your https address and signed, so your server can tell they are ours.
The code is kept only as a one-way fingerprint, so nobody at Meetowt can read it. It waits for its one send encrypted, and that copy is deleted the moment Meta answers.
The number is kept as a one-way fingerprint and its last three digits, for the log. Requests are deleted after 30 days.
Your Meta token and app secret are kept encrypted and are never shown again, not even to your administrators.
No. A developer account is for codes only. A company that has a workspace finds Verify in Admin, then Verify, with the same keys and routes.
You do, directly, on your own Meta account: each WhatsApp message is Meta's to bill. Meetowt's own price is per successful check, and free during early access.
Nothing, ever. It never reaches Meta, and its code is always 000000.
$0.015 for each successful check is 30% of Twilio Verify's $0.05 base fee.
Yes, on the status page, which shows whether Meetowt and Verify's sending to Meta are working right now.
A developer account takes a minute, a test key needs no WhatsApp number, and it is free during early access.