For AI agents: markdown of this page — /docs-content-en/entities/catalog-skus/search.md documentation index — /llms.txt
Search SKUs
POST /v1/catalog-skus/search
Search parent products using the conditions passed in the request body.
Unlike GET /v1/catalog-skus, the filter, select, sort, limit, and offset parameters are passed in the JSON body rather than in the query string — conditions across several fields are expressed as a nested structure. Like the list, search requires filter.iblockId — without this field the request returns 400. The response format is the same as for the list.
Request fields (body)
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
filter |
object | yes | — | Filtering conditions. The iblockId key is required — the product catalog ID from GET /v1/catalogs. The type key accepts one exact number: 3 — parent products with offers, 6 — without offers.Filtering syntax. Example: { "iblockId": 25, "type": 3 } |
select |
string[] | no | — | Field selection: ["iblockId", "id", "name", "type"]. If the parameter is passed, it must include iblockId and id. Without select, the response carries a reduced set of fields: the symbolic code, texts, sort order, and external code are returned only when listed explicitly — SKU fields lists which ones. A catalog property is requested by its own name: ["iblockId", "id", "name", "property295"] |
sort |
string | no | — | Sort field. The - prefix means descending: "-id" |
limit |
number | no | 50 |
Number of records (up to 5000) |
offset |
number | no | 0 |
Offset from the start of the result set. Combined with a date-range filter wider than 14 days, the request is rejected — see UNSTABLE_OFFSET_PAGINATION in the "Errors" section |
autoWindow |
boolean | no | 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/catalog-skus/search" \
-H "X-Api-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"filter": { "iblockId": 25, "type": 3 },
"sort": "-id",
"limit": 2
}'
curl — OAuth application
curl -X POST "https://vibecode.bitrix24.com/v1/catalog-skus/search" \
-H "X-Api-Key: YOUR_APP_KEY" \
-H "Authorization: Bearer USER_SESSION_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"filter": { "iblockId": 25, "type": 3 },
"sort": "-id",
"limit": 2
}'
JavaScript — personal key
const res = await fetch('https://vibecode.bitrix24.com/v1/catalog-skus/search', {
method: 'POST',
headers: {
'X-Api-Key': 'YOUR_API_KEY',
'Content-Type': 'application/json',
},
body: JSON.stringify({
filter: { iblockId: 25, type: 3 },
sort: '-id',
limit: 2,
}),
})
const { success, data, meta } = await res.json()
console.log(`Found: ${meta.total}`)
JavaScript — OAuth application
const res = await fetch('https://vibecode.bitrix24.com/v1/catalog-skus/search', {
method: 'POST',
headers: {
'X-Api-Key': 'YOUR_APP_KEY',
'Authorization': 'Bearer USER_SESSION_TOKEN',
'Content-Type': 'application/json',
},
body: JSON.stringify({
filter: { iblockId: 25, type: 3 },
sort: '-id',
limit: 2,
}),
})
const { success, data, meta } = await res.json()
Response fields
| Field | Type | Description |
|---|---|---|
success |
boolean | Always true on success |
data |
array | Array of parent products. For the fields of each item, see SKU fields |
meta.total |
number | 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 |
meta.warnings |
array | Warnings about select. Present when select contains a name that is not in the field reference: an item { code: "UNKNOWN_SELECT_FIELD", message, field }, and no value for that name is included in the response |
The meta fields sit next to data, not inside it. Paginate using meta.hasMore: a data array whose length equals limit can still be the last page.
Response example
{
"success": true,
"data": [
{
"id": 7205,
"iblockId": 25,
"iblockSectionId": 19,
"name": "Basic hoodie",
"type": 3,
"active": true,
"available": true,
"bundle": false,
"createdBy": 1295,
"modifiedBy": 1295,
"dateActiveFrom": null,
"dateActiveTo": null,
"dateCreate": "2026-10-08T18:45:34.000Z",
"timestampX": "2026-10-08T18:45:36.000Z"
},
{
"id": 7203,
"iblockId": 25,
"iblockSectionId": null,
"name": "Basic T-shirt",
"type": 3,
"active": true,
"available": true,
"bundle": false,
"createdBy": 1295,
"modifiedBy": 1295,
"dateActiveFrom": null,
"dateActiveTo": null,
"dateCreate": "2026-10-08T18:45:34.000Z",
"timestampX": "2026-10-08T18:45:35.000Z"
}
],
"meta": {
"total": 14,
"hasMore": true,
"durationMs": 140
}
}
With a date-range filter wider than 14 days, meta additionally returns autoWindowed, windowCount, and batchWaves:
{
"success": true,
"data": [ /* ... */ ],
"meta": {
"total": 12,
"hasMore": true,
"autoWindowed": true,
"windowCount": 301,
"batchWaves": 7,
"durationMs": 4058
}
}
Error response example
400 — the required filter was not passed:
{
"success": false,
"error": {
"code": "MISSING_REQUIRED_FILTER",
"message": "POST /v1/catalog-skus/search requires filter fields: iblockId. Example body: { \"filter\": {\"iblockId\":\"...\"} }"
}
}
Errors
| HTTP | Code | Description |
|---|---|---|
| 400 | MISSING_REQUIRED_FILTER |
The required filter.iblockId filter was not passed. The request is rejected before Bitrix24 is called — the message contains the name of the missing field and a request body example |
| 400 | UNSUPPORTED_FILTER |
The filter.type key was passed as something other than a single number 3 or 6 — another number, an operator, or an array |
| 422 | BITRIX_ERROR |
iblockId points to an offer catalog (productType is not allowed for this catalog) |
| 422 | BITRIX_ERROR |
iblockId is not a catalog (iblock is not catalog) |
| 422 | BITRIX_ERROR |
select was passed without iblockId (Required select fields: iblockId) |
| 422 | BITRIX_ERROR |
select was passed without id (Required select fields: id) |
| 400 | UNKNOWN_FILTER_FIELD |
Filtering by a field the parent product does not have. The message contains the list of available fields |
| 400 | UNKNOWN_SORT_FIELD |
Sorting by a field the parent product does not have. The message contains the list of available 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. Fetch 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 catalog scope |
| 401 | MISSING_API_KEY |
The X-Api-Key header was not passed |
| 429 | RATE_LIMITED |
Rate limit exceeded: 300 requests per minute per portal, all API keys of the portal share one limit. The exact value arrives in the x-ratelimit-limit header (the cap is divided across replicas). Retry after the delay in the Retry-After header |
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.