Skip to main content
One-Time Codes in the sidebar is where you set up the template a login code goes out on. It is deliberately not part of Templates, because almost nothing on that page applies here.

​
You do not write this one

An authentication template is the one kind whose words are not yours. Meta writes them:
394812 is your verification code. For your security, do not share this code. Expires in 10 minutes.
You cannot change that wording, add your brand to it, or explain anything in it. That is a mercy rather than a restriction — OTP is the one message where wording is a liability, and Meta has already argued with every phishing pattern there is. What you choose is three things, and the preview beside them updates as you do.
​
1–90 minutes
Ten by default: long enough to find your phone, short enough that a screenshot in a group chat is worthless by the time it matters. WhatsApp says this line in the customer’s own language, so it costs you no words.
​
on / off
Appends “For your security, do not share this code.” On by default.
​
Copy code / One-tap
  • Copy code — they tap, then paste. Works everywhere, needs no integration, and is the right answer for almost everyone.
  • One-tap autofill — hands the code straight to your Android app. Needs your app’s package name and signing hash, which the form asks for. Meta refuses the template without them, so you would otherwise find out at review rather than at login.
There is no “no button” option, and that is Meta’s rule rather than ours: a code template must carry exactly one button, of one of these two kinds.

​
Getting it approved

A new template is a draft — ours, not Meta’s, and it cannot send anything. Open it and press Submit for review. Authentication templates are usually approved within minutes, because Meta wrote the content and has little to argue with.
Submit needs a connected number. Meta reviews a template against your WhatsApp Business Account, so until one is connected there is nothing to submit it to — the button says so on hover.
Once submitted, the settings lock. Meta reviewed a specific configuration and the API offers no way to change it underneath them. To use different settings, delete it and make another.

​
Sending a code

Through the API, when your own system has generated one — see Send a one-time code. The short version:
We do not generate, store, expire or check the code. That stays yours.

​
Deleting one

Either from the row’s ⋯ menu in the list, or from Delete on the template’s own page.
This removes it from Meta as well as from here, and there are two consequences worth knowing before you click:
  • Anything calling the API with that template’s name stops working.
  • Meta will not let the name be used again for 30 days. If you are replacing a template, give the new one a different name.
A draft that never reached Meta has neither consequence — nothing is using it, and the name stays free.

​
What this costs

Authentication is priced separately from marketing and utility, and a code sent to another country costs many times a domestic one — on Meta’s Indian card, more than twentyfold. Your own figures are on the usage page, split by category and country, which is the only way anyone notices a login flow that has quietly gone international.