Skip to main content
An authentication template sends a one-time passcode, for sign-in, account recovery or confirming a transaction. It’s the only category allowed to carry a passcode, and the strictest: the wording is fixed by Meta, you add only the code and optional security and expiry lines, and the message includes a button that copies or fills in the code.
In Flowella. Partly supported. Flowella can send authentication templates through the Flowella API, with a different code for each recipient. Flowella’s editor can’t add passcode buttons, so create the template in WhatsApp Manager. A HubSpot workflow can’t send passcodes.

What the message contains

Authentication templates can’t contain links, media or emojis, and each variable is limited to 15 characters. Use only digits and letters in the code.

Button types

On iOS 26 and later, iOS offers the code as a keyboard suggestion from the notification, for every authentication template, with no work on your side. Earlier iOS versions don’t autofill, so copy code is the safe choice when you don’t build a native Android app.
If your Android app starts the one-tap or zero-tap handshake with PendingIntent, move to Meta’s OTP Android SDK before 31 January 2027, when Meta retires the PendingIntent method.

Linked devices

WhatsApp delivers authentication messages only to the person’s main phone. On linked devices, such as WhatsApp Web or a tablet, the message is hidden and the person is asked to check their phone. You can’t turn this off.

Time-to-live

Set the time-to-live no longer than your code is valid, so nobody receives a code that has already expired. Flowella has no time-to-live setting. If you need a custom value, set it on the template in WhatsApp Manager.

Price

Authentication messages are charged per delivered message, with volume tiers. In some markets, Meta charges a higher authentication-international rate when an eligible business sends codes to numbers in that market. See WhatsApp pricing.

Create one in WhatsApp Manager

1

Start a template

In WhatsApp Manager, click Create template and choose Authentication. You can also start from an authentication template in Meta’s library.
2

Choose the options

Choose the button type, and turn on the security line and expiry line if you want them. For one-tap or zero-tap, add your Android app’s package name and signature hash.
3

Submit

Choose the languages and submit. Meta writes the wording, so review is usually quick.
The template then appears on Flowella’s Templates page, ready to send through the API.

Send passcodes from Flowella

Your app creates the code, stores it with an expiry, and calls POST /v1/templates/send with the code as the body variable and the button value. Flowella refuses a code longer than 15 characters before it reaches Meta. For a full walkthrough with resend and lockout rules, see Send one-time passcodes.

Good practice

  • Confirm the number first. Make sure the WhatsApp number belongs to the person before you send a code to it.
  • Tell people the code is coming on WhatsApp, especially if you also offer SMS or email.
  • Show that you received it. When the person pastes the code, or your app receives it, confirm on screen.
  • Don’t send codes in marketing or utility templates. Meta rejects templates that carry passcodes in the wrong category, from the first day of the following month. See Template categories.

Send one-time passcodes

The Flowella API walkthrough.

Template library

Meta’s ready-made templates.

Template fundamentals

Names, languages, statuses and limits.

WhatsApp pricing

Authentication rates and the international rate.
Checked against Meta’s documentation on 18 November 2026: Authentication templates, Template categorization and Time-to-live.
Last modified on November 18, 2026