Authentication Templates
Authentication Templates in Chatarmin
What is this?
Authentication templates are a third WhatsApp template category alongside Marketing and Utility. They exist for one job: sending a one-time passcode (OTP) to your customer. Meta controls the message text, you control the code and a few settings, and the customer gets a tap-to-copy button to grab the code.
💳 How they're priced
Authentication templates are priced like Utility templates, which is cheaper than Marketing templates. So if you're currently sending login or confirmation codes through a Marketing template, switching to an Authentication template lowers your per-message cost.
⚙️ What you can and can't configure
One variable: the code. The template carries a single variable, the OTP itself. You pass the code at send time.
The body text is fixed. Meta provides static authentication text based on the template's language. You can't change the wording.
OTP button. The template includes an OTP button that works like a copy-code button, so the customer copies the code with one tap.
Expiry in minutes. You set an expiry time (in minutes) when you create the template. Once that time passes, Meta removes the button that holds the code.
Security recommendation (optional). You can enable a security recommendation, which adds a line below the code along the lines of "For your security, do not share this code."
Where you can use them
Authentication templates work both in Flows and through our APIs, so you can fire them from an automated flow or trigger them directly from your own system.
When to use Authentication templates
App or account login (sending a login code).
Order or delivery confirmations that rely on a verification code.
Any step where the customer needs to confirm an action with a one-time code.
When NOT to use Authentication templates
For promotions, offers, or campaigns. Use a Marketing template instead.
For transactional info that isn't a code (order status, shipping updates, invoices). Use a Utility template.
The body text is fixed, so if you need custom wording around the code, an Authentication template isn't the right fit.
Good to know: Once the expiry time you set runs out, Meta removes the code button automatically. The customer can't copy an expired code, so set the expiry to match how long the code is actually valid in your system.
You're all set and good to go!