We are making changes to the WhatsApp Business Platform pricing model. See Pricing Updates on the WhatsApp Business Platform.
The OTP Android SDK is in beta and features a simplified workflow for implementing one-tap and zero-tap authentication templates. You can learn how to use it below.
One-tap autofill authentication templates allow you to send a one-time password or code along with an one-tap autofill button to your users. When a WhatsApp user taps the autofill button, the WhatsApp client triggers an activity which opens your app and delivers it the password or code.
One-tap autofill button authentication templates consist of:
One-tap autofill buttons are only supported on Android. If you send an authentication template to a WhatsApp user who is using a non-Android device, the WhatsApp client will display a copy code button instead.
URLs, media, and emojis are not supported.
Use the WhatsApp Business Account > Message Templates endpoint to create authentication templates.
POST /<WHATSAPP_BUSINESS_ACCOUNT_ID>/message_templates
{ "name": "<TEMPLATE_NAME>", "language": "<TEMPLATE_LANGUAGE>", "category": "authentication", "message_send_ttl_seconds": <TIME_T0_LIVE>, // Optional "components": [ { "type": "body", "add_security_recommendation": <SECURITY_RECOMMENDATION> // Optional }, { "type": "footer", "code_expiration_minutes": <CODE_EXPIRATION> // Optional }, { "type": "buttons", "buttons": [ { "type": "otp", "otp_type": "one_tap", "text": "<COPY_CODE_BUTTON_TEXT>", // Optional "autofill_text": "<AUTOFILL_BUTTON_TEXT>", // Optional "supported_apps": [ { "package_name": "<PACKAGE_NAME>", "signature_hash": "<SIGNATURE_HASH>" } ] } ] } ] }
Note that in your template creation request the button type is designated as otp
, but upon creation the button type will be set to url
. You can confirm this by performing a GET request on a newly created authentication template and analyzing its components.
Placeholder | Description | Example Value |
---|---|---|
String | Optional. One-tap autofill button label text. If omitted, the autofill text will default to a pre-set value, localized to the template's language. For example, Maximum 25 characters. |
|
Integer | Optional. Indicates the number of minutes the password or code is valid. If included, the code expiration warning and this value will be displayed in the delivered message. The button will be disabled in the delivered message the indicated number of minutes from when the message was sent. If omitted, the code expiration warning will not be displayed in the delivered message. In addition, the button will be disabled 10 minutes from when the message was sent. Minimum 1, maximum 90. |
|
String | Optional. Copy code button label text. If omitted, the text will default to a pre-set value localized to the template's language. For example, If included, the authentication template message will display a copy code button with this text if the message fails the eligibility check. Maximum 25 characters. |
|
String | Required. Your Android app's package name. The string must have at least two segments (one or more dots), and each segment must start with a letter. All characters must be alphanumeric or an underscore [ If using Graph API version 20.0 or older, you can define your app's package name outside of the Maximum 224 characters. |
|
Boolean | Optional. Set to |
|
String | Required. Your app signing key hash. See App Signing Key Hash below. All characters must be either alphanumeric, If using Graph API version 20.0 or older, you can define your app's signature hash outside of the Must be exactly 11 characters. |
|
String | Required. Template language and locale code. |
|
String | Required. Template name. Maximum 512 characters. |
|
Integer | Optional. Authentication message time-to-live value, in seconds. See Customizing Time-To-Live. |
|
This example creates a template named "authentication_code_autofill_button" categorized as authentication
with all optional text strings enabled and a one-tap autofill button.
curl 'https://graph.facebook.com/v21.0
/102290129340398/message_templates' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer EAAJB...' \
-d '
{
"name": "authentication_code_autofill_button",
"language": "en_US",
"category": "authentication",
"message_send_ttl_seconds": 60,
"components": [
{
"type": "body",
"add_security_recommendation": true
},
{
"type": "footer",
"code_expiration_minutes": 10
},
{
"type": "buttons",
"buttons": [
{
"type": "otp",
"otp_type": "one_tap",
"text": "Copy Code",
"autofill_text": "Autofill",
"package_name": "com.example.luckyshrub",
"signature_hash": "K8a/AINcGX7"
}
]
}
]
}'
{ "id": "594425479261596", "status": "PENDING", "category": "AUTHENTICATION" }
You must include your app signing key hash in your post body.
To calculate your hash, follow Google's instructions for computing your app's hash string.
Alternatively, if you follow Google's instructions and download your app signing key certificate (step 1), you can use your certificate with the sms_retriever_hash_v9.sh shell script to compute the hash. For example:
./sms_retriever_hash_v9.sh --package "com.example.myapplication" --keystore ~/.android/debug.keystore
The supported_apps
array allows you define pairs of app package names and signing key hashes for up to 5 apps. This can be useful if you have different app builds and want each of them to be able to initiate the handshake:
"buttons": [ { "type": "otp", ... "supported_apps": [ { "package_name": "<PACKAGE_NAME_1>", "signature_hash": "<SIGNATURE_HASH_1>" }, { "package_name": "<PACKAGE_NAME_2>", "signature_hash": "<SIGNATURE_HASH_2>" }, ... ] } ]
Alternatively, if you have only a single app, you can define the app's package name and signing key hash as buttons object properties, but this is not recommened as we will stop supporting this method at a future date:
"buttons": [ { "type": "otp", ... "package_name": "<PACKAGE_NAME>", "signature_hash": "<SIGNATURE_HASH>" } ]
You must signal to the WhatsApp client to expect imminent delivery of a password or code. You can do this by initiating a "handshake".
A handshake is an Android intent and public class that you implement but that the WhatsApp client can start.
When a user in your app requests a one-time password or verification code and chooses for it to be delivered to their WhatsApp number, first perform the handshake, then call our API to send the authentication template message. When the WhatsApp client receives the message, it will perform an eligibility check, and if there are no errors, start the intent and display the message to the user. Finally, when the user taps the message's one-tap autofill button, we automatically load your app and pass it the password or code.
If you do not perform a handshake before sending the message, or the message fails an eligibility check, the delivered message will display a copy code button instead of a one-tap button.
The WhatsApp client performs the following checks when it receives an authentication template message. If any check fails, the one-tap autofill button will be replaced with a copy code button.
code_expiration_minutes
property, if present).package_name
property in the components
array upon template creation) matches the package name set on the intent. The match is determined through the getCreatorPackage
method called in the PendingIntent
object provided by your application.supported_apps
initiated a handshake in the last 10 minutes (or the number of minutes indicated by the template's code_expiration_minutes
property, if present).signature_hash
property in the components array upon template creation) matches your installed app's signing key hash.Android notifications indicating receipt of a WhatsApp authentication template message will only appear on the user's Android device if:
The OTP Android SDK is available in beta. It can be used to perform handshakes, as well as other functions in both one-tap and zero-tap authentication templates.
To access SDK functionality, add the following configuration to your Gradle file:
dependencies { … implementation 'com.whatsapp.otp:whatsapp-otp-android-sdk:0.1.0' … }
To your repositories, add mavenCentral()
:
repositories { … mavenCentral() … }
Declare an activity and intent filter that can receive the one-time password or code. The intent filter must have the action name com.whatsapp.otp.OTP_RETRIEVED
.
<activity android:name=".ReceiveCodeActivity" android:enabled="true" android:exported="true" android:launchMode="standard"> <intent-filter> <action android:name="com.whatsapp.otp.OTP_RETRIEVED" /> </intent-filter> </activity>
This is the activity that the WhatsApp app or WhatsApp Business app will start once the authentication template message is received and it passes all eligibility checks.
Define the activity public class and instantiate a WhatsAppOtpIncomingIntentHandler
object to handle the intent, validate the OTP code, and handle errors.
public class ReceiveCodeActivity extends AppCompatActivity { @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); WhatsAppOtpIncomingIntentHandler incomingIntentHandler = new WhatsAppOtpIncomingIntentHandler(); incomingIntentHandler.processOtpCode( intent, // call your function to validate (code) -> validateCode(code), // call your function to handle errors (error, exception) -> handleError(error, exception)); }
Define the activity public class that can accept the code once it has been passed to your app.
public class ReceiveCodeActivity extends AppCompatActivity { @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); Intent intent = getIntent(); // retrieve PendingIntent from extras bundle PendingIntent pendingIntent = intent.getParcelableExtra("_ci_"); // verify source of the pendingIntent String pendingIntentCreatorPackage = pendingIntent.getCreatorPackage(); // check if creatorPackage is "com.whatsapp" -> WA consumer app Or // "com.whatsapp.w4b" -> WA business app if ("com.whatsapp".equals(creatorPackage) || "com.whatsapp.w4b".equals(creatorPackage)) { // use OTP code String otpCode = intent.getStringExtra("code"); } } }
Performing a handshake can be done by instantiating the WhatsAppOtpHandler
object and passing in your context to the .sendOtpIntentToWhatsApp()
method:
WhatsAppOtpHandler whatsAppOtpHandler = new WhatsAppOtpHandler(); whatsAppOtpHandler.sendOtpIntentToWhatsApp(context);
This example demonstrates one way to initiate a handshake with the WhatsApp client.
public void sendOtpIntentToWhatsApp() { // Send OTP_REQUESTED intent to both WA and WA Business App sendOtpIntentToWhatsApp("com.whatsapp"); sendOtpIntentToWhatsApp("com.whatsapp.w4b"); } private void sendOtpIntentToWhatsApp(String packageName) { /** * Starting with Build.VERSION_CODES.S, it will be required to explicitly * specify the mutability of PendingIntents on creation with either * (@link #FLAG_IMMUTABLE} or FLAG_MUTABLE */ int flags = Build.VERSION.SDK_INT >= Build.VERSION_CODES.S ? FLAG_IMMUTABLE : 0; PendingIntent pi = PendingIntent.getActivity( getApplicationContext(), 0, new Intent(), flags); // Send OTP_REQUESTED intent to WhatsApp Intent intentToWhatsApp = new Intent(); intentToWhatsApp.setPackage(packageName); intentToWhatsApp.setAction("com.whatsapp.otp.OTP_REQUESTED"); // WA will use this to verify the identity of the caller app. Bundle extras = intentToWhatsApp.getExtras(); if (extras == null) { extras = new Bundle(); } extras.putParcelable("_ci_", pi); intentToWhatsApp.putExtras(extras); getApplicationContext().sendBroadcast(intentToWhatsApp); }
You can check WhatsApp installation before offering WhatsApp as an option if you expect both WhatsApp and your app to be on the same device.
First, you need to add the following to your AndroidManifest.xml
file:
<queries> <package android:name="com.whatsapp"/> <package android:name="com.whatsapp.w4b"/> </queries>
Instantiate the WhatsAppOtpHandler
object:
WhatsAppOtpHandler whatsAppOtpHandler = new WhatsAppOtpHandler();
Check if the WhatsApp client is installed by passing the isWhatsAppInstalled
method as the clause in an If
statement:
If (whatsAppOtpHandler.isWhatsAppInstalled(context)) { // ... do something }
if (this.isWhatsAppInstalled(context)) { // ... do something } public boolean isWhatsAppInstalled(final @NonNull Context context){ return isWhatsAppInstalled(context, "com.whatsapp") || isWhatsAppInstalled(context, "com.whatsapp.w4b"); } public boolean isWhatsAppInstalled(final @NonNull Context context, final @NonNull String type){ final Intent intent = new Intent(); intent.setPackage(type); intent.setAction("com.whatsapp.otp.OTP_REQUESTED"); PackageManager packageManager = context.getPackageManager(); List<ResolveInfo> receivers = packageManager.queryBroadcastReceivers(intent, 0); return !receivers.isEmpty(); } }
Use Cloud API or On-Premises API to send authentication template messages.
Note that you must first initiate a handshake between your app and the WhatsApp client. See Handshake above.
See Error Signals that can help with debugging.
See our WhatsApp One-Time Password (OTP) Sample App for Android on Github. The sample app demonstrates how to send and receive OTP passwords and codes via the API, how to integrate the one-tap autofill and copy code buttons, how to create a template, and how to spin up a sample server.