# Postman collection

To test and debug requests, you can use the Swagger section of the API on [your channel page in dashboard](https://panel.whapi.cloud/dashboard) or the [Postman collection](https://www.postman.com/whapi-cloud-api/whapi-cloud-api/collection/huzy5nm/whatsapp-api?action=share\&creator=33022403\&active-environment=33022403-69de92fb-d4d1-40ff-877e-f9fc886fd1b1).

{% embed url="<https://www.postman.com/whapi-cloud-api/workspace/whapi-cloud-api/collection/33022403-51773546-5ab6-4a7f-9eb2-9f9ec02a5068?action=share&creator=33022403&active-environment=33022403-69de92fb-d4d1-40ff-877e-f9fc886fd1b1>" %}
Postman Whapi.Cloud API Collection
{% endembed %}

### How to Always Stay Updated with the Latest Postman Collection

To ensure you always have the most up-to-date version of the Whapi.Cloud API collection, follow the steps below.

1. Open the [**WhatsApp API Collection**](https://www.postman.com/whapi-cloud-api/workspace/whapi-cloud-api/collection/33022403-51773546-5ab6-4a7f-9eb2-9f9ec02a5068?action=share\&active-environment=33022403-69de92fb-d4d1-40ff-877e-f9fc886fd1b1\&creator=33022403) in Postman Web.
2. Click **Fork →** select your workspace → **Fork**. You can press the shortcut keys to do this: `Ctrl + Alt + F`

<figure><img src="/files/Tec3wW3wxWtQjRP9G3uP" alt=""><figcaption><p>Create a fork</p></figcaption></figure>

3. When creating a Fork, be sure to leave the check mark next to the item: `Watch original collection`. &#x20;

<figure><img src="/files/CUZwLWyFQkHMvLHmtqxK" alt=""><figcaption></figcaption></figure>

3.1. Or, in the top bar of your Fork, enable **Watch** (to subscribe to updates).

<div data-full-width="false"><figure><img src="/files/EL7mK6MEJpDLaYUN6vuk" alt="" width="563"><figcaption></figcaption></figure></div>

4. Keep the proposed variable environment

<figure><img src="/files/nA40OKBOiwLktzQc11IZ" alt=""><figcaption></figcaption></figure>

5. When updates are released, you’ll see **Pull changes** in your fork — click **Pull**, then **Merge** (if prompted).\
   This keeps your fork in your workspace while syncing all new updates.

#### If You Previously Imported the Collection

If you used **Run in Postman** or **Import**, that version will **not update automatically**.\
To fix this, delete the old imported collection and create a **Fork** from the link above, following the steps above.

***

### Environment Variables

The collection uses the variable **`baseUrl`**.\
Create an **Environment** in Postman and set your preferred `baseUrl` (e.g., `https://gate.whapi.cloud`)

Specify your **channel token** in the authorization header by entering the value of a global variable.

<figure><img src="/files/vp0PwUm6GIoHGnkEviP3" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/CGRV7jxGNN1hPtCTESQY" alt=""><figcaption><p>Set Variable</p></figcaption></figure>

If you automatically create a Fork from our website, don't forget to specify Whapi Env as your primary environment:

<figure><img src="/files/2glTfAgVjblfPhng5c2s" alt=""><figcaption></figcaption></figure>

Now you can select any API method in the collection and start sending requests. For convenience, all methods are listed in the same order as they are discussed in the [API Documentation](https://whapi.readme.io/reference/sendmessagetext). You can make any changes to these methods to simplify their testing and response handling.

<figure><img src="/files/PoTZl6hGf3SEcZZc3lyR" alt=""><figcaption><p>Test any API Call: Send text message</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://support.whapi.cloud/help-desk/getting-started/api-docs/postman-collection.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.