GET /v1/files/{file_id}/versions — Atom Files Developers

← API referenceFiles & delivery · API access unavailable

API REFERENCE / FILES

`GET` /v1/files/{file_id}/versions

List versions visible to the caller so an app can present history or resolve an expected-version conflict without silently overwriting another edit.

Request fields

Location	Field	Type	Required	Description
Header	`Authorization`	string	Yes	Credential scoped to the authorized resource.
Path	`file_id`	string	Yes	Stable Atom file ID.
Query	`cursor`	string	No	Opaque pagination cursor.

Request example

Example request

GET /v1/files/file_789/versions
Authorization: Bearer <scoped token>

HTTP status codes

Status	Meaning
`200 OK`	Success response shown below.
`400 Bad Request`	Invalid pagination cursor.
`401 Unauthorized`	Missing, expired, or invalid credential.
`403 Forbidden`	Credential is valid but lacks the required scope or role.
`404 Not Found`	File does not exist or is not visible to this caller.
`429 Too Many Requests`	Rate limit reached; honor Retry-After when provided.
`503 Service Unavailable`	Service temporarily unavailable; retry safely.

Response fields

Field	Type	Example
`items`	object[]	[1 shown]
`items[].id`	string	ver_012
`items[].file_id`	string	file_789
`items[].size_bytes`	integer	4194304
`items[].created_at`	string (date-time)	2026-10-20T18:00:00Z
`next_cursor`	string \| null	null

Response example

Example response

200 OK
Content-Type: application/json

{
  "items": [
    {
      "id": "ver_012",
      "file_id": "file_789",
      "size_bytes": 4194304,
      "created_at": "2026-10-20T18:00:00Z"
    }
  ],
  "next_cursor": null
}

How it works

Path parameterfile_idStable Atom file identifier.

AuthorizationResults are limited to versions the caller may read; knowing an ID is not access.

PaginationRequired for a public release; cursor semantics have not been specified.