> 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.md).

# 3.2. Resend SMS token

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

Resends the SMS token if the customer hasn't received it or the token has expired.

## URL Parameters

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

## Request Body

| Field   | Type   | Required | Description                             | Example            |
| ------- | ------ | :------: | --------------------------------------- | ------------------ |
| `phone` | string |    Yes   | Phone number registered in the proposal | `"+5511991818065"` |

## Request Example

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

## Success Response (200 OK)

```json
{
  "message": "SMS token resent successfully",
  "phone": "+5511991818065",
  "expires_at": "2025-10-13T20:51:12.079Z"
}
```

### Response Fields

| Field        | Type              | Description                              |
| ------------ | ----------------- | ---------------------------------------- |
| `message`    | string            | Confirmation message                     |
| `phone`      | string            | Phone number to which the SMS was resent |
| `expires_at` | string (ISO 8601) | Expiration date/time of the new token    |

## Possible Errors

| Code | Message                                     |
| ---- | ------------------------------------------- |
| 400  | Phone number not registered in the proposal |
| 404  | Proposal not found                          |
| 409  | Proposal in an invalid state for resending  |

## Notes

* The newly generated token **replaces the previous one** and is valid for 10 minutes
* The `phone` must be exactly the same number registered in the step [Send Contact](/api-reference/apis-en/proposal-flow/post-proposals-contact.md)
* For resending via WhatsApp, use [POST /proposals/{id}/contact/resend-token/whatsapp](/api-reference/apis-en/proposal-flow/post-proposals-resend-token-whatsapp.md)

{% 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.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.