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

# 3. Validate SMS token

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

Validates the SMS code received by the customer to confirm the phone number.

## URL Parameters

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

## Request Body

| Field   | Type   | Required | Description                     | Example            |
| ------- | ------ | :------: | ------------------------------- | ------------------ |
| `token` | string |    Yes   | 6-digit code received by SMS    | `"036322"`         |
| `phone` | string |    Yes   | Phone used in the previous step | `"+5511991818065"` |

## Request Example

```json
{
  "token": "036322",
  "phone": "+5511991818065"
}
```

## Success Response (201 Created)

```json
{
  "message": "Token validated successfully",
  "proposal_id": "99afc6ce-4720-4746-9cf6-0a23e85cdf75",
  "status": "TOKEN_VALIDATED",
  "phone": "+5511991818065",
  "email": "lucas@bullcredtech.com"
}
```

### Response Fields

| Field         | Type          | Description                   |
| ------------- | ------------- | ----------------------------- |
| `message`     | string        | Confirmation message          |
| `proposal_id` | string (UUID) | Proposal ID                   |
| `status`      | string        | New status: `TOKEN_VALIDATED` |
| `phone`       | string        | Validated phone               |
| `email`       | string        | Associated email              |

## Possible Errors

| Code | Message                      |
| ---- | ---------------------------- |
| 400  | Invalid or expired SMS token |
| 404  | Proposal not found           |

## Notes

* After **3 incorrect attempts**, the token is invalidated and a new one must be requested
* Expired token requires requesting a new code via:
  * [POST /contact/resend-token](/api-reference/apis-en/proposal-flow/post-proposals-resend-token.md) — Resend by SMS
  * [POST /contact/resend-token/whatsapp](/api-reference/apis-en/proposal-flow/post-proposals-resend-token-whatsapp.md) — Resend by WhatsApp
* The phone number provided must be exactly the same as the one used in step 2
* After successful validation, consent is recorded automatically

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

Request the credit analysis: [POST /proposals/{id}/credit-analysis](/api-reference/apis-en/proposal-flow/post-proposals-credit-analysis.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-validate-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.