> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/system-settings/account-settings/whatsapp-web.md).

# WhatsApp Web

To use the integration of the **WhatsApp Web in SprintHub**, it is necessary to contract an API intermediary platform, with the currently supported ones being **Z-API** or **UAZAPI**. These platforms are responsible for establishing the connection between your WhatsApp number and SprintHub.

### Prerequisites

Before starting the setup, it is necessary to:

* Have an active SprintHub account;
* Contract an account on Z-API or UAZAPI;
* Have an active WhatsApp number;
* Have access to the mobile device where WhatsApp is connected.

***

### 1. Contract Z-API or UAZAPI

Before carrying out the integration, it is necessary to contract one of the platforms approved by SprintHub, responsible for mediating the connection between WhatsApp and the platform.

Choose one of the options below and follow the respective contracting and initial setup tutorial:

* **Z-API**

{% content-ref url="/pages/b449fdb5708ce42a6bc96f552923275f250e7bc0" %}
[Integrations - Z-API](/en/topics/integrations/integrations-z-api.md)
{% endcontent-ref %}

* **UAZAPI**

{% content-ref url="/pages/d12efd6f3bbd615f56b24431974f84bf79e1a331" %}
[Integrations - uazapiGO](/en/topics/integrations/integrations-uazapigo.md)
{% endcontent-ref %}

⚠️ **Important:** Contracting Z-API or UAZAPI is mandatory to use the WhatsApp Web integration in SprintHub.

***

### 2. Access SprintHub settings

In the SprintHub menu, go to:

**Settings → Account Settings → WhatsApp Web → Add Account**

### 3. Select the desired integration

Choose the option corresponding to the contracted provider:

* Z-API
* UAZAPI

Then, enter the data requested by SprintHub, such as:

* Instance ID;
* Security token;
* Instance URL (when applicable).

***

### 4. Connect WhatsApp

Open WhatsApp on the phone and follow the path:

**Menu → Connected devices → Connect a device**

Then, scan the QR Code provided by the contracted platform and wait for synchronization.

<figure><img src="/files/887f979f89b2db7ebb5eba242ef89fcefc972dbd" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/1d12aee84895b1faa8aa28333c4b0b21b2b915a2" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/31f6a2aeaa7d197b8155ad35c07a6e3a4c83cc3f" alt=""><figcaption></figcaption></figure>

***

### 5. Finish setup

After the connection is completed:

* Save the settings;
* Check whether the account status appears as **Connected**;
* Perform a test of sending and receiving messages.

***

### Notes

* SprintHub does not provide the infrastructure for Z-API or UAZAPI, so it is necessary to contract the service directly with the chosen provider.
* If the connection is lost, it may be necessary to scan the QR Code again.
* It is recommended to keep the mobile device connected to the internet to avoid interruptions in synchronization.


---

# 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://docs.sprinthub.com/en/topics/system-settings/account-settings/whatsapp-web.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.
