[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-entities\u002Fstorages\u002Fsearch":3,"docs-tabs-entities\u002Fstorages\u002Fsearch":6},{"content":4,"lastmod":5},"\n## Search storages\n\n`POST \u002Fv1\u002Fstorages\u002Fsearch`\n\nSearch storages with filters. Equivalent to `GET \u002Fv1\u002Fstorages` with a filter, but via POST — conditions across several fields are passed in the request body. Filtering by exact field match, auto-pagination when `limit > 50`.\n\n**Result ordering.** With no sort the list arrives ascending by `id`. `id` is appended to your sort as a final key, so the order is always total and unambiguous and paging over it is repeatable: when sorting by a non-unique field, a row sharing that value could otherwise land on two pages at once, or drop out, at a page boundary. If you sort by `id` yourself, your direction is preserved.\n\n## Request fields (body)\n\n| Parameter | Type | Default | Description |\n|----------|-----|-----------|---------|\n| `filter` | object | — | Exact equality and `$in` (IN set) only, over the fields `id`, `name`, `code`, `entityType`, `entityId`. Operators (`>`, `>=`, `\u003C`, `\u003C=`, `!`, `%`, `$ne`, `$contains`, `$nin`) and other fields (for example `rootFolderId`) are not supported — returns `400 UNSUPPORTED_FILTER`.\u003Cbr>[Filtering syntax](\u002Fdocs\u002Ffiltering). Example: `{ \"entityType\": \"group\" }` |\n| `limit` | number | `50` | Number of records (up to 5000). When `limit > 50` the request is assembled automatically from several pages on the server side |\n| `offset` | number | `0` | Skip N records. Used to read result sets larger than 5000 records: increase `offset` by the size of the batch you received until `meta.hasMore` turns `false` |\n| `select` | string[] | — | Field selection: `[\"id\", \"name\"]`. Only the listed fields are returned |\n| `sort` | string | — | Sort field, a leading minus means descending: `\"-id\"`. The fields that change the order are `id`, `name`, `entityType`, `entityId`, `rootFolderId` (verified live). The method also accepts `code` and `module`, but on the accounts we checked those fields hold the same value for every storage, so ordering by them changes nothing |\n| `order` | object | — | The same in object form: `{ \"id\": \"desc\" }`. When both are passed, `sort` wins |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fstorages\u002Fsearch\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"filter\": { \"entityType\": \"group\" },\n    \"limit\": 10\n  }'\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fstorages\u002Fsearch\" \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"filter\": { \"entityType\": \"group\" },\n    \"limit\": 10\n  }'\n```\n\n### JavaScript — personal key\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fstorages\u002Fsearch', {\n  method: 'POST',\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n    'Content-Type': 'application\u002Fjson',\n  },\n  body: JSON.stringify({\n    filter: { entityType: 'group' },\n    limit: 10,\n  }),\n})\n\nconst { success, data, meta } = await res.json()\nconsole.log(`Total storages matching the filter: ${meta.total}`)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fstorages\u002Fsearch', {\n  method: 'POST',\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n    'Content-Type': 'application\u002Fjson',\n  },\n  body: JSON.stringify({\n    filter: { entityType: 'group' },\n    limit: 10,\n  }),\n})\n\nconst { success, data, meta } = await res.json()\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|---------|\n| `success` | boolean | Always `true` on success |\n| `data` | array | Array of storages (see [Storage fields](\u002Fdocs\u002Fentities\u002Fstorages\u002Ffields)) |\n| `meta.total` | number | Total number of records matching the filter |\n| `meta.hasMore` | boolean | Whether there are more records beyond `limit` |\n| `meta.durationMs` | number | Request duration in milliseconds |\n\nThe `meta` fields sit next to `data`, not inside it. Page through the results using `meta.hasMore`: a `data` length equal to `limit` does not rule out the last page.\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": [\n    {\n      \"id\": 3,\n      \"name\": \"Private visible group\",\n      \"code\": null,\n      \"module\": \"disk\",\n      \"entityType\": \"group\",\n      \"entityId\": \"1\",\n      \"rootFolderId\": 3\n    },\n    {\n      \"id\": 113,\n      \"name\": \"test111\",\n      \"code\": null,\n      \"module\": \"disk\",\n      \"entityType\": \"group\",\n      \"entityId\": \"11\",\n      \"rootFolderId\": 787\n    }\n  ],\n  \"meta\": {\n    \"total\": 38,\n    \"hasMore\": true,\n    \"durationMs\": 150\n  }\n}\n```\n\n## Error response example\n\n400 — operator or unsupported field in the filter:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"UNSUPPORTED_FILTER\",\n    \"message\": \"UNSUPPORTED_FILTER: operators are not supported on 'storages' (near 'id'). Its Bitrix24 method (disk.storage.getlist) filters by exact match only — operators are silently ignored by Bitrix24. Use exact match (field: value) or $in (field: {$in: [...]}) on: id, name, code, entityType, entityId.\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|---------|\n| 400 | `UNSUPPORTED_FILTER` | Operator or unsupported field in the filter. Filter by exact equality or `$in` on `id`, `name`, `code`, `entityType`, `entityId` |\n| 403 | `SCOPE_DENIED` | The API key does not have the `disk` scope |\n| 401 | `TOKEN_MISSING` | The API key has no configured tokens |\n| 429 | `RATE_LIMITED` | Rate limit exceeded: 300 requests per minute per portal. All API keys of the portal share one limit. The current limit is returned in the `x-ratelimit-limit` header. Retry after the delay in the `Retry-After` header |\n\nFor the full list of common API errors, see [Errors](\u002Fdocs\u002Ferrors).\n\n## See also\n\n- [List storages](\u002Fdocs\u002Fentities\u002Fstorages\u002Flist)\n- [Get storage](\u002Fdocs\u002Fentities\u002Fstorages\u002Fget)\n- [Storage fields](\u002Fdocs\u002Fentities\u002Fstorages\u002Ffields)\n- [Filtering syntax](\u002Fdocs\u002Ffiltering)\n- [Limits and optimization](\u002Fdocs\u002Foptimization)\n","2026-10-23",{},1794739426793]