File version history

GET /v1/files/:id/versions

Bitrix24 method: disk.file.getVersions. Scope: disk.

Newest versions come first. History may be incomplete: uploads by the same author within about five minutes join, while Bitrix24 settings limit the number of versions and retention time. The test account retained three versions on 2026-10-07. Access only through a task or chat attachment is not recognized here, even when reading the file itself works. Plans without history return 403 DISK_HISTORY_UNAVAILABLE.

Parameters: limit 1..50 (default 50), integer offset >=0 (default 0). Filter only by id, size, name, createdAt, createdBy; entity-system operators: $gt, $gte, $lt, $lte, $ne, $contains, $in, $nin, prefixes >, >=, <, <=, !, %. Unknown fields or a non-object filter return 400 INVALID_PARAMS. Use bracket query syntax.

curl -H "X-Api-Key: YOUR_API_KEY" https://vibecode.bitrix24.com/v1/files/7/versions\
  --get --data-urlencode 'filter[size][$gte]=1'

{
  "success": true,
  "data": [
    {
      "id": 9,
      "fileId": 7,
      "size": 3,
      "name": "report.txt",
      "contentGeneration": 2,
      "createdAt": "2026-10-07T07:00:00.000Z",
      "createdBy": 1,
      "downloadUrl": "/v1/files/7/versions/9/download"
    }
  ],
  "meta": {
    "total": 1,
    "limit": 50,
    "offset": 0,
    "hasMore": false,
    "nextOffset": null
  }
}

Errors: 400 invalid ID or parameters, 401 missing key, 403 missing disk scope or Bitrix24 permission, 404 missing record, 422 Bitrix24 business refusal. READONLY keys can read but cannot upload or restore. On writes, 502 DISK_OUTCOME_UNKNOWN requires reading the file before any retry.