For AI agents: markdown of this page — /docs-content-en/entities/payments/search.md documentation index — /llms.txt
Search payments
POST /v1/payments/search
Searches payments with filtering and auto-pagination. Equivalent to GET /v1/payments, but parameters are passed in the POST request body — suited for complex requests with many conditions.
Request fields (body)
| Parameter | Type | Default | Description |
|---|---|---|---|
filter |
object | — | Filtering by payment fields. Filtering syntax |
limit |
number | 50 |
Number of records (up to 5000) |
offset |
number | 0 |
Skip N records. Together with a date-range filter wider than 14 days it is rejected — see UNSTABLE_OFFSET_PAGINATION in the "Errors" section |
select |
string[] | — | Field selection: ["id", "orderId", "sum", "paid"] |
order |
object | — | Sorting: { "id": "desc" } |
autoWindow |
boolean | true |
Split the result set into weekly windows when filtering by a date range wider than 14 days. false disables splitting |
Examples
curl — personal key
curl -X POST "https://vibecode.bitrix24.com/v1/payments/search" \
-H "X-Api-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"filter": { "orderId": 19, "paid": true },
"limit": 10,
"select": ["id", "orderId", "sum", "currency", "paid", "datePaid"]
}'
curl — OAuth application
curl -X POST "https://vibecode.bitrix24.com/v1/payments/search" \
-H "X-Api-Key: YOUR_APP_KEY" \
-H "Authorization: Bearer USER_SESSION_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"filter": { "orderId": 19, "paid": true },
"limit": 10,
"select": ["id", "orderId", "sum", "currency", "paid", "datePaid"]
}'
JavaScript — personal key
const res = await fetch('https://vibecode.bitrix24.com/v1/payments/search', {
method: 'POST',
headers: {
'X-Api-Key': 'YOUR_API_KEY',
'Content-Type': 'application/json',
},
body: JSON.stringify({
filter: { orderId: 19, paid: true },
limit: 10,
select: ['id', 'orderId', 'sum', 'currency', 'paid', 'datePaid'],
}),
})
const { success, data, meta } = await res.json()
console.log('Found:', meta.total)
JavaScript — OAuth application
const res = await fetch('https://vibecode.bitrix24.com/v1/payments/search', {
method: 'POST',
headers: {
'X-Api-Key': 'YOUR_APP_KEY',
'Authorization': 'Bearer USER_SESSION_TOKEN',
'Content-Type': 'application/json',
},
body: JSON.stringify({
filter: { orderId: 19, paid: true },
limit: 10,
select: ['id', 'orderId', 'sum', 'currency', 'paid', 'datePaid'],
}),
})
const { success, data, meta } = await res.json()
Response fields
| Field | Type | Description |
|---|---|---|
success |
boolean | Always true on success |
data |
array | Array of payments |
meta.total |
number | How many records matched the filter |
meta.hasMore |
boolean | Whether there is a next page |
meta.durationMs |
number | Request duration in milliseconds |
meta.autoWindowed |
boolean | true if the result set was split into time windows |
meta.windowCount |
number | Number of windows. Present with autoWindowed: true |
meta.batchWaves |
number | Number of parallel request waves. Present with autoWindowed: true |
The meta fields sit next to data, not inside it. Pages must be walked by meta.hasMore: a data length equal to limit does not rule out the last page.
Response example
{
"success": true,
"data": [
{
"id": 17,
"orderId": 19,
"sum": 0,
"currency": "USD",
"paid": false,
"datePaid": "2020-05-14T20:00:00.000Z"
}
],
"meta": {
"total": 1,
"hasMore": false,
"durationMs": 132
}
}
With a date-range filter wider than 14 days, meta additionally returns autoWindowed, windowCount, and batchWaves:
{
"success": true,
"data": [ /* ... */ ],
"meta": {
"total": 99,
"hasMore": true,
"autoWindowed": true,
"windowCount": 339,
"batchWaves": 7,
"durationMs": 2618
}
}
Error response example
400 — filter by a non-existent field:
{
"success": false,
"error": {
"code": "UNKNOWN_FILTER_FIELD",
"message": "Unknown filter field 'foo' for entity 'payments'. Available: id, orderId, paySystemId, sum, currency, paid, ..."
}
}
Errors
| HTTP | Code | Description |
|---|---|---|
| 400 | UNKNOWN_FILTER_FIELD |
Filtering by a field that is not in the payment schema |
| 400 | UNSTABLE_OFFSET_PAGINATION |
offset greater than zero together with a date-range filter wider than 14 days. Two different retrieval algorithms produce inconsistent results, so the request is rejected. Take everything in a single request with limit up to 5000, or pass autoWindow: false with sorting by id, or split the date range into parts yourself |
| 403 | SCOPE_DENIED |
The API key does not have the sale scope |
| 401 | TOKEN_MISSING |
The API key has no configured tokens |
Full list of common API errors — Errors.
Known specifics
Time-window splitting. A date-range filter wider than 14 days is automatically split into weekly windows executed in parallel waves, so the result set bypasses the ceiling of 5000 records per call. meta then returns autoWindowed: true, the number of windows windowCount, and the number of waves batchWaves. The autoWindow: false parameter disables splitting. While splitting is active, an offset greater than zero is rejected with UNSTABLE_OFFSET_PAGINATION.
select limits the fields in the response. If select is passed, each element of data[] contains only the listed fields. Without select, all payment fields are returned.
The isReturn field is a string. It accepts "N", "Y" and "P" — filtering and updating work on these values.