Skip to main content
An authentication template delivers a one-time code — for a login, a sign-up or confirming an action. It is a message template like any other, except that Meta writes the wording and you choose only how it behaves. Your own system generates the code and checks it when the customer types it back; Watx only delivers it. To create one, open WhatsApp → Templates → New Template → Start from scratch and set Category to Authentication. The editor changes completely: there is no body, header, footer or button list to fill in.

​
What the customer sees

Meta writes the message and translates it into the template’s language. The editor shows it read-only:
123456 is your verification code. For your security, do not share this code.
Below it, Meta adds an expiry line if you set one, and a button that copies or fills in the code.

​
Settings

​
How they get the code

​
Your Android app

One-tap and zero-tap deliver the code into your own Android app, so Meta needs to know which app it is.
  • App package name — for example com.example.myapp: at least two parts separated by dots, each starting with a letter, using only letters, digits and underscores.
  • App signature hash — exactly 11 characters: letters, digits, +, / or =.
  • Add another app — up to five. Use it for the same app signed another way: a build installed from Google Play and a test build you install yourself have different signature hashes. Pasting several values separated by commas fills one row each. The same package name and hash cannot be listed twice.
  • Autofill label (optional) — up to 25 characters.
If you do not have an Android app, use Copy code.

​
Zero-tap terms

Zero-tap shows a checkbox, I accept the zero-tap terms. Zero-tap is subject to the WhatsApp Business Terms of Service, and your customers must expect the code to be filled in for them automatically. Meta refuses a zero-tap template without it, and Watx never ticks it for you.

​
Submitting

Submit for Approval works as for any template, and the template goes through the same statuses. If something is missing — a package name, a hash of the wrong length, the zero-tap terms — the submit is refused with a sentence naming it. Sync from Meta brings authentication templates created elsewhere into Watx with their button type and every app they list, so editing one later keeps its settings.

​
Sending a code

Send a code through the Watx API: POST /v1/messages with type: "template", the template’s name and language, and the code as the only parameter.
The code can be up to 15 characters. WhatsApp puts it in the message and on the copy or autofill button. The key needs the messages:send scope — see Authentication and the API introduction. The code icon on the template’s card in WhatsApp → Templates shows this exact request for that template, with a runnable curl.
The inbox, campaigns, automations and flows have no field for a one-time code, so an authentication template cannot be sent from them: a send from the inbox fails, and a campaign using one is refused before anything is sent.