/developers
Developer docsAtom Files ↗
← API referenceBrowse & search · API access unavailable
API REFERENCE / BROWSE & SEARCH

GET /v1/folders/{folder_id}

Read one folder’s name, visible parent, revision, and effective access role.

Request fields

LocationFieldTypeRequiredDescription
HeaderAuthorizationstringYesCredential scoped to the authorized resource.
Pathfolder_idstringYesStable Atom folder ID.

Request example

Example request
GET /v1/folders/folder_123
Authorization: Bearer <scoped token>

HTTP status codes

StatusMeaning
200 OKSuccess response shown below.
401 UnauthorizedMissing, expired, or invalid credential.
403 ForbiddenCredential is valid but lacks the required scope or role.
404 Not FoundFolder does not exist or is not visible.
429 Too Many RequestsRate limit reached; honor Retry-After when provided.
503 Service UnavailableService temporarily unavailable; retry safely.

Response fields

FieldTypeExample
idstringfolder_123
namestringProjects
parent_idnullnull
revisionstringrev_007
access_rolestring (enum)editor
Allowed values · closed enumviewereditorowner

Response example

Example response
200 OK
Content-Type: application/json

{
  "id": "folder_123",
  "name": "Projects",
  "parent_id": null,
  "revision": "rev_007",
  "access_role": "editor"
}

How it works

Use one role rather than a stored list of action flags: viewer can browse and read; editor can also add, edit, and remove items inside the folder; owner can additionally rename, move, or trash the folder and manage sharing. The API derives permitted actions from this role and checks token scopes separately. A folder ID never bypasses a grant. A null parent_id means no parent is visible to this caller; it does not prove the folder is the owner’s top-level folder.