> For the complete documentation index, see [llms.txt](https://helpdocs.ycloud.com/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.ycloud.com/help-center/whatsapp-basics/message-templates/authentication-message-templates/zero-click-authentication-template.md).

# Zero-Click Authentication Template

The Zero-Tap Authentication Template allows your users to receive one-time passwords or codes via WhatsApp without leaving your application.

When a user in your app requests a password or code and you provide that password or code using the Zero-Tap Authentication Template, the WhatsApp client simply broadcasts the included password or code, which your app can capture immediately using a broadcast receiver.

From the user's perspective, they request a password or code in your app, and it automatically appears in your app. If your app users happen to be viewing messages in the WhatsApp client, they will only see a message displaying the default pinned text: *\<code> is your verification code.*

Like the One-Tap Autofill Button Authentication Template, when the WhatsApp client receives a template message containing the user's password or code, we perform a series of eligibility checks. If the message fails this check and we cannot broadcast the password or code, the message will display a One-Tap Autofill Button or Copy Code button. Therefore, when you create a Zero-Tap Authentication Template, you must include One-Tap Autofill and Copy Code buttons in the post body payload, even if the user may never see one of the buttons.

<figure><img src="/files/6dzHi9eCslCxlLhi60TX" alt="" width="563"><figcaption></figcaption></figure>

#### Limitations <a href="#limitations" id="limitations"></a>

Zero-Tap is only supported on Android. If you send a Zero-Tap Authentication Template to a WhatsApp user with a non-Android device, WhatsApp will display a Copy Code button.

URLs, media, and emojis are not supported.

## **Template Creation**

### **Example Request Creation via API (Copy Code)**

{% embed url="<https://docs.ycloud.com/reference/whatsapp-template-creation-examples#zero-tap-authentication-template>" %}

### Manually Create via [YCloud Console](https://www.ycloud.com/console/#/app/whatsApp/template)

{% content-ref url="/pages/XxgpY4qxMvM1NrPUeoEj" %}
[Create Template](/help-center/whatsapp-accounts-management/template-management/create-template.md)
{% endcontent-ref %}

## **Sending Authentication Template Messages**

Use YCloud [WhatsApp API](https://docs.ycloud.com/reference/whatsapp_message-send-directly) to send authentication template messages.

Please note that if you are sending an authentication template with a One-Tap Autofill Button, you must first initiate a handshake between your app and WhatsApp Messenger or WhatsApp Business. See the handshake below.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpdocs.ycloud.com/help-center/whatsapp-basics/message-templates/authentication-message-templates/zero-click-authentication-template.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.