> For the complete documentation index, see [llms.txt](https://docs.bullcredtech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bullcredtech.com/api-reference/apis-en/proposal-flow/post-proposals-resend-token-whatsapp.md).

# 3.1. Resend token via WhatsApp

**POST** `/proposals/{proposalId}/contact/resend-token/whatsapp`

Resends the validation code via WhatsApp as an alternative to SMS. Useful when the customer does not receive the SMS or prefers WhatsApp.

## URL parameters

| Parameter    | Type          | Description |
| ------------ | ------------- | ----------- |
| `proposalId` | string (UUID) | Proposal ID |

## Request Body

| Field         | Type   | Required | Description                          | Example            |
| ------------- | ------ | :------: | ------------------------------------ | ------------------ |
| `phoneNumber` | string |    Yes   | Phone number in international format | `"+5511991818065"` |

## Request Example

```json
{
  "phoneNumber": "+5511991818065"
}
```

## Success Response (200 OK)

```json
{
  "message": "WhatsApp token sent successfully",
  "phone": "+5511991818065",
  "expires_at": "2025-10-13T20:51:12.079Z",
  "messageId": "zenvia_message_id_123",
  "logId": "whatsapp_log_456"
}
```

### Response Fields

| Field        | Type              | Description                       |
| ------------ | ----------------- | --------------------------------- |
| `message`    | string            | Confirmation message              |
| `phone`      | string            | Formatted phone number            |
| `expires_at` | string (ISO 8601) | Token expiration date/time        |
| `messageId`  | string            | Message ID in the Zenvia provider |
| `logId`      | string            | Internal log ID for tracking      |

## Possible Errors

| Code | Error Code               | Message                                    |
| ---- | ------------------------ | ------------------------------------------ |
| 400  | `INVALID_PHONE_NUMBER`   | Invalid phone number                       |
| 404  | `PROPOSAL_NOT_FOUND`     | Proposal not found                         |
| 409  | `PROPOSAL_INVALID_STATE` | Proposal in an invalid state for resending |
| 500  | `WHATSAPP_SERVICE_ERROR` | WhatsApp service error                     |

## Notes

* The newly generated token **replaces the previous one** and is valid for 10 minutes
* The token is identical to the one sent by SMS — it can be validated normally at `/contact/validate-token`
* The `phoneNumber` must be the same number registered in the proposal
* Use this endpoint when the customer does not receive the SMS or prefers WhatsApp

{% hint style="success" %}
**Next Step**

Validate the received code: [POST /proposals/{id}/contact/validate-token](/api-reference/apis-en/proposal-flow/post-proposals-validate-token.md)
{% endhint %}


---

# 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.bullcredtech.com/api-reference/apis-en/proposal-flow/post-proposals-resend-token-whatsapp.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.