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

# 7.2. Cancel proposal

**POST** `/proposals/{proposalId}/cancel`

Cancels an existing proposal before disbursement. If there is an active application linked to the contract, the API also tries to cancel that application in Celcoin.

{% hint style="warning" %}
**When cancellation is allowed**

This route can only be used when the proposal is in `CONTRACT_GENERATED` or `AWAITING_SIGNATURE`.
{% endhint %}

## URL Parameters

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

## Headers

| Header          | Required | Description                                     |
| --------------- | :------: | ----------------------------------------------- |
| `Authorization` |    Yes   | Bearer token from the authorized partner source |

## Request Body

This endpoint does not accept a body.

## Business Rules

* Cancellation is allowed only before disbursement
* The proposal must be in `CONTRACT_GENERATED` or `AWAITING_SIGNATURE`
* Cancellation is irreversible
* If there is an active application in Celcoin, the API tries to cancel it automatically
* Even if the cancellation in Celcoin fails, the proposal can be marked as `CANCELED`

## Request Example

```http
POST /proposals/99afc6ce-4720-4746-9cf6-0a23e85cdf75/cancel HTTP/1.1
Authorization: Bearer your_token
```

## Success Response (200 OK)

The endpoint returns the updated proposal data.

```json
{
  "id": "99afc6ce-4720-4746-9cf6-0a23e85cdf75",
  "cpf": "12345678909",
  "full_name": "CLIENT NAME",
  "status": "CANCELED",
  "updated_at": "2025-12-01T15:30:00.000Z"
}
```

### Response Fields

| Field        | Type              | Description                                     |
| ------------ | ----------------- | ----------------------------------------------- |
| `id`         | string (UUID)     | Unique proposal ID                              |
| `cpf`        | string            | Customer CPF                                    |
| `full_name`  | string            | Client's full name                              |
| `status`     | string            | Final status of the proposal after cancellation |
| `updated_at` | string (ISO 8601) | Date and time of the last update                |

## Possible Errors

| Code | Message                                                                                    |
| ---- | ------------------------------------------------------------------------------------------ |
| 400  | Proposal can only be canceled in the statuses "Contract Generated" or "Awaiting Signature" |
| 404  | Proposal not found                                                                         |

## Notes

* The expected final status is `CANCELED`
* This endpoint represents cancellation before disbursement
* After disbursement, any cancellations enter the flow `CANCELLED_BY_USER`, not in this route

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

After cancellation, consult [GET /proposals/{proposalId}](/api-reference/apis-en/queries/get-proposals-by-id.md) or monitor the webhooks to confirm the final status of the proposal.
{% 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-cancel.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.