Skip to main content

​
Accepted formats

Tawked verifies Saudi mobile numbers only. Send to in any of these forms; it is stored and echoed back as E.164. Anything else answers 422 invalid_destination. The deprecated field phone is still accepted as an alias for to, and to wins when both are present.

​
Language

lang picks the message language. Only the literal value en selects English; anything else, including a missing field, means Arabic.

​
Sender identity

The sender name and the message wording come from your reviewed application, never from the request. That is what the review is for: the person receiving the code sees your brand, and nobody can send under it with a stray key.

​
Autofill-ready SMS

Phones can read a code straight out of the SMS when the message ends with the right lines. Tawked adds them for you, after the human-readable text:
  • @domain #code, the last line, is what iOS AutoFill and the WebOTP API read. The domain is derived from your application’s reviewed website and is read-only; switch the line on or off per application.
  • The app hash line is for Google’s SMS Retriever on Android. Set the 11-character hash per application.
  • The optional autofill field on start (web, android or none) picks which lines go out on that one send. Omit it to send every line the application has configured.
The whole message must stay under 140 bytes for Android’s SMS Retriever, and Arabic SMS is billed per 70-character segment. The domain line adds about 25 characters, which can turn one segment into two. The dashboard preview shows the segment count.
Autofill lines are out of scope for WhatsApp: its message is a fixed Meta template with no room for either.