For AI agents: markdown of this page — /docs-content-en/entities/quotes/aggregate.md documentation index — /llms.txt
Aggregate quotes
POST /v1/quotes/aggregate
Count, sum, average, minimum, and maximum over CRM quotes with filtering and grouping.
Standard fields:
amount— quote amount (numeric aggregation makes sense)stageId— stage (forgroupBy)assignedById— assignee (forgroupBy)
User fields (UF): UF fields of type integer, double, money — for numeric functions; UF of any type — for groupBy. The full list of UF fields for a specific Bitrix24 account is returned in the INVALID_PARAMS error message if you pass a non-existent name.
Request fields (body)
| Parameter | Type | Required | Description |
|---|---|---|---|
aggregate |
array | no | Array of aggregations. Each element: { "field": "amount", "function": "sum" }. Functions: count, sum, avg, min, max. For count, the field is "*". Without the array — only count |
filter |
object | no | Filtering by GET /v1/quotes/fields fields. Filter syntax |
groupBy |
string | string[] | no | Field or array of fields to group by (maximum 5). Allowed values — from the list above |
Examples
curl — personal key
curl -X POST "https://vibecode.bitrix24.com/v1/quotes/aggregate" \
-H "X-Api-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"aggregate": [
{ "field": "amount", "function": "sum" },
{ "field": "amount", "function": "avg" }
],
"filter": { "assignedById": 1 },
"groupBy": "stageId"
}'
curl — OAuth app
curl -X POST "https://vibecode.bitrix24.com/v1/quotes/aggregate" \
-H "X-Api-Key: YOUR_APP_KEY" \
-H "Authorization: Bearer USER_SESSION_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"aggregate": [
{ "field": "amount", "function": "sum" },
{ "field": "amount", "function": "avg" }
],
"filter": { "assignedById": 1 },
"groupBy": "stageId"
}'
JavaScript — personal key
const res = await fetch('https://vibecode.bitrix24.com/v1/quotes/aggregate', {
method: 'POST',
headers: {
'X-Api-Key': 'YOUR_API_KEY',
'Content-Type': 'application/json',
},
body: JSON.stringify({
aggregate: [
{ field: 'amount', function: 'sum' },
{ field: 'amount', function: 'avg' },
],
filter: { assignedById: 1 },
groupBy: 'stageId',
}),
})
const { success, data } = await res.json()
console.log('Total quotes:', data.count)
console.log('By stage:', data.groups)
JavaScript — OAuth app
const res = await fetch('https://vibecode.bitrix24.com/v1/quotes/aggregate', {
method: 'POST',
headers: {
'X-Api-Key': 'YOUR_APP_KEY',
'Authorization': 'Bearer USER_SESSION_TOKEN',
'Content-Type': 'application/json',
},
body: JSON.stringify({
aggregate: [
{ field: 'amount', function: 'sum' },
{ field: 'amount', function: 'avg' },
],
filter: { assignedById: 1 },
groupBy: 'stageId',
}),
})
const { success, data } = await res.json()
To group by multiple fields, pass an array:
"groupBy": ["stageId", "assignedById"](maximum 5).
Other scenarios
Count records — count with field "*", the fastest request without fetching records. Without the aggregate array the result is the same:
{ "aggregate": [{ "field": "*", "function": "count" }] }
Working with user fields (UF) — sum over a UF + grouping by another UF:
{
"aggregate": [{ "field": "UF_CRM_DISCOUNT", "function": "sum" }],
"groupBy": "UF_CRM_PRIORITY"
}
Response fields
| Field | Type | Description |
|---|---|---|
success |
boolean | Always true on success |
data.count |
number | Total number of records matching the filter |
data.aggregates |
object | Aggregation results: { "amount": { "sum": 90000, "avg": 2500 } } |
data.groups |
array | Groups (only with groupBy). Each element: grouping fields + count + aggregates |
data.meta.totalRecords |
number | Total number of records matching the filter |
data.meta.recordsProcessed |
number | How many records were processed for numeric aggregations (maximum 5000) |
data.meta.truncated |
boolean | true if more than 5000 records matched the filter |
Response example
Response to the main request (aggregations + groupBy: "stageId"):
{
"success": true,
"data": {
"count": 36,
"aggregates": {
"amount": { "sum": 90000, "avg": 2500 }
},
"groups": [
{
"stageId": "DRAFT",
"count": 20,
"aggregates": { "amount": { "sum": 50000 } }
},
{
"stageId": "APPROVED",
"count": 16,
"aggregates": { "amount": { "sum": 40000 } }
}
],
"meta": {
"totalRecords": 36,
"recordsProcessed": 36,
"truncated": false
}
}
}
Without groupBy, the data.groups field is absent from the response.
Error response example
400 — invalid function name, non-existent field, or groupBy on a non-aggregatable field:
{
"success": false,
"error": {
"code": "INVALID_PARAMS",
"message": "Field 'foo' not found. Available numeric fields: amount, stageId, assignedById"
}
}
Errors
| HTTP | Code | Description |
|---|---|---|
| 400 | INVALID_PARAMS |
Invalid function name, non-existent field, non-numeric field in sum/avg/min/max, groupBy on a non-aggregatable field, or more than 5 fields in groupBy |
| 401 | TOKEN_MISSING |
The API key has no configured tokens |
| 403 | SCOPE_DENIED |
The API key lacks the crm scope |
Full list of common API errors — Errors.
Known specifics
count vs numeric functions. count is computed in a single Bitrix24 call at any data volume. The functions sum/avg/min/max fetch records page by page (maximum 5000) and compute on the Vibecode side — if more than 5000 records match the filter, meta.truncated will be true and the aggregation runs over the first 5000. For exact counters on large selections, use count or narrow the filter.
Money fields. UF fields of type money are stored in the format "amount|currency" ("1500|USD") — the aggregate extracts the numeric part automatically, so you can sum without parsing.
Filtering by UF works. In filter you can pass any fields — standard and user fields, of any type. For example, { "filter": { "ufCrm_1234": "value" } } returns the number of quotes with that UF value.
See also
- List quotes — retrieve records with filtering
- Search quotes — POST request with filters
- Filter syntax
- Limits and optimization — rate limits