For AI agents: markdown of this page — /docs-content-en/entities/quotes/update.md documentation index — /llms.txt
Update a quote
PATCH /v1/quotes/:id
Updates fields of an existing CRM quote. Pass only the fields being changed. Full list in the field reference, including user fields (ufCrm_*).
Frequently updated fields
| Parameter | Type | Description |
|---|---|---|
stageId |
string | Status: DRAFT, SENT, APPROVED. List: GET /v1/statuses?filter[entityId]=QUOTE_STATUS |
opportunity |
number | Quote amount. Pass it together with isManualOpportunity: true, otherwise Bitrix24 will recalculate the amount from line items (the flag is stored as Y/N; the boolean is converted automatically) |
assignedById |
number | Assignee. List: GET /v1/users |
title |
string | Name |
closedate |
datetime | Close date |
Field names. In responses, fields are returned in camelCase:
amount,currency,beginDate,closeDate. On write, both variants are accepted — these camelCase names and the B24-nativeopportunity/currencyId/begindate/closedate: the API layer maps them to the name Bitrix24 expects.
Examples
curl — personal key
curl -X PATCH "https://vibecode.bitrix24.com/v1/quotes/412" \
-H "X-Api-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"stageId": "APPROVED",
"isManualOpportunity": true,
"opportunity": 145000
}'
curl — OAuth app
curl -X PATCH "https://vibecode.bitrix24.com/v1/quotes/412" \
-H "X-Api-Key: YOUR_APP_KEY" \
-H "Authorization: Bearer USER_SESSION_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"stageId": "APPROVED",
"isManualOpportunity": true,
"opportunity": 145000
}'
JavaScript — personal key
const res = await fetch('https://vibecode.bitrix24.com/v1/quotes/412', {
method: 'PATCH',
headers: {
'X-Api-Key': 'YOUR_API_KEY',
'Content-Type': 'application/json',
},
body: JSON.stringify({
stageId: 'APPROVED',
isManualOpportunity: true,
opportunity: 145000,
}),
})
const { success, data } = await res.json()
JavaScript — OAuth app
const res = await fetch('https://vibecode.bitrix24.com/v1/quotes/412', {
method: 'PATCH',
headers: {
'X-Api-Key': 'YOUR_APP_KEY',
'Authorization': 'Bearer USER_SESSION_TOKEN',
'Content-Type': 'application/json',
},
body: JSON.stringify({
stageId: 'APPROVED',
isManualOpportunity: true,
opportunity: 145000,
}),
})
const { success, data } = await res.json()
Response fields
| Field | Type | Description |
|---|---|---|
data |
object | The updated quote object with all fields — see Fields |
The updated quote object with all fields — see Quote fields.
Response example
{
"success": true,
"data": {
"id": 412,
"title": "Quote for server hardware",
"amount": 145000,
"currency": "USD",
"stageId": "APPROVED",
"dealId": 741,
"assignedById": 1,
"updatedTime": "2026-04-15T15:10:00.000Z"
}
}
Error response example
404 — quote not found:
{
"success": false,
"error": {
"code": "ENTITY_NOT_FOUND",
"message": "Item not found"
}
}
Errors
| HTTP | Code | Description |
|---|---|---|
| 404 | ENTITY_NOT_FOUND |
Quote not found |
| 403 | ACCESS_DENIED |
No access to the quote |
| 400 | INVALID_REQUEST |
Invalid fields |
| 403 | SCOPE_DENIED |
The API key lacks the crm scope |
| 401 | TOKEN_MISSING |
The API key has no configured tokens |
Full list of common API errors — Errors.
See also
- Working with files in CRM fields
- Get a quote — current field values
- Quote fields — which fields can be changed
- Batch — bulk update of quotes
- Limits and optimization — rate limits