> For the complete documentation index, see [llms.txt](https://brpex.gitbook.io/brpex-crm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brpex.gitbook.io/brpex-crm/api/envio-de-campanhas/envio-de-campanha-por-status-arquivo.md).

# Envio de campanha por Status (arquivo)

## Send Status Text

<mark style="color:green;">`POST`</mark> `https://{SUBDOMAIN}.brpex.com/api/v1 /send-status-text`

#### Headers

| Name                                      | Type   | Description                                     |
| ----------------------------------------- | ------ | ----------------------------------------------- |
| token\*<mark style="color:red;">\*</mark> | String | As tokens são geradas na configuração do canal. |

#### Request Body

| Name                                     | Type   | Description                                                               |
| ---------------------------------------- | ------ | ------------------------------------------------------------------------- |
| text                                     | String | Texto que será exibido como legenda nas campanhas via Status do WhatsApp. |
| file\*<mark style="color:red;">\*</mark> | String | Arquivo de imagem que será exibida no Status do WhatsApp.                 |

{% tabs %}
{% tab title="200: OK Campanha recebida para fila de envios" %}

```javascript
{
    // Response
}
```

{% endtab %}

{% tab title="400: Bad Request Arquivo não acessível ou inválido. " %}

```javascript
{
    // Response
}
```

{% endtab %}

{% tab title="401: Unauthorized Erro de autenticação. Verifique o token informado." %}

```javascript
{
    // Response
}
```

{% endtab %}

{% tab title="422: Unprocessable Entity Informações insuficientes. Você precisa enviar todos os campos obrigatórios." %}

```javascript
{
    // Response
}
```

{% endtab %}
{% endtabs %}


---

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

```
GET https://brpex.gitbook.io/brpex-crm/api/envio-de-campanhas/envio-de-campanha-por-status-arquivo.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.