For AI agents: markdown of this page — /docs-content-en/entities/orders/search.md documentation index — /llms.txt

Search orders

POST /v1/orders/search

Search orders with filtering, sorting, and auto-pagination. Equivalent to GET /v1/orders, but parameters are passed in the POST request body — suited for complex requests with many conditions.

Request fields (body)

Field Type Default Description
filter object — Filtering by GET /v1/orders/fields fields.
Filter 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", "price", "currency", "statusId"]
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

Terminal 
curl -X POST "https://vibecode.bitrix24.com/v1/orders/search" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "filter": { "statusId": "N", "payed": false },
    "limit": 10,
    "select": ["id", "price", "currency", "statusId", "dateInsert"]
  }'

curl — OAuth application

Terminal 
curl -X POST "https://vibecode.bitrix24.com/v1/orders/search" \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "filter": { "statusId": "N", "payed": false },
    "limit": 10,
    "select": ["id", "price", "currency", "statusId", "dateInsert"]
  }'

JavaScript — personal key

javascript 
const res = await fetch('https://vibecode.bitrix24.com/v1/orders/search', {
  method: 'POST',
  headers: {
    'X-Api-Key': 'YOUR_API_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    filter: { statusId: 'N', payed: false },
    limit: 10,
    select: ['id', 'price', 'currency', 'statusId', 'dateInsert'],
  }),
})

const { success, data, meta } = await res.json()
console.log('Found:', meta.total)

JavaScript — OAuth application

javascript 
const res = await fetch('https://vibecode.bitrix24.com/v1/orders/search', {
  method: 'POST',
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    filter: { statusId: 'N', payed: false },
    limit: 10,
    select: ['id', 'price', 'currency', 'statusId', 'dateInsert'],
  }),
})

const { success, data, meta } = await res.json()

Response fields

Field Type Description
success boolean Always true on success
data array Array of orders (fields — see Order fields)
meta.total number Total number of records matching the filter
meta.hasMore boolean Whether there are more records beyond limit
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.

The URL of any order from the data array — its id:

https://<portal>.bitrix24.com/shop/orders/details/<id>/

<portal> — the Bitrix24 account domain. Access is restricted by the employee's permissions in Bitrix24.

Response example

JSON 
{
  "success": true,
  "data": [
    {
      "id": 845,
      "price": 100,
      "currency": "USD",
      "statusId": "N",
      "dateInsert": "2026-04-21T06:48:16.000Z"
    },
    {
      "id": 841,
      "price": 100.5,
      "currency": "USD",
      "statusId": "N",
      "dateInsert": "2026-04-04T20:02:28.000Z"
    }
  ],
  "meta": {
    "total": 181,
    "hasMore": true,
    "durationMs": 211
  }
}

With a date-range filter wider than 14 days, meta additionally returns autoWindowed, windowCount, and batchWaves:

JSON 
{
  "success": true,
  "data": [ /* ... */ ],
  "meta": {
    "total": 37,
    "hasMore": true,
    "autoWindowed": true,
    "windowCount": 131,
    "batchWaves": 3,
    "durationMs": 1299
  }
}

Error response example

400 — filter by a non-existent field:

JSON 
{
  "success": false,
  "error": {
    "code": "UNKNOWN_FILTER_FIELD",
    "message": "Unknown filter field 'foo' for entity 'orders'. Available: id, accountNumber, price, currency, statusId, userId, ..."
  }
}

Errors

HTTP Code Description
400 UNKNOWN_FILTER_FIELD Filter by a field not present in the schema. Field list: GET /v1/orders/fields
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[] will contain only the listed fields. Without select, all order fields are returned.

See also