GET /v1/grants — Atom Files Developers

← API referenceAccess · API access unavailable

API REFERENCE / ACCESS

`GET` /v1/grants

Let an owner inspect which integrations can access which folders.

Request fields

Location	Field	Type	Required	Description
Header	`Authorization`	string	Yes	Credential scoped to the authorized resource.
Query	`cursor`	string	No	Opaque pagination cursor.

Request example

Example request

GET /v1/grants
Authorization: Bearer <owner 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.
`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	grant_123
`items[].folder_id`	string	folder_123
`items[].integration_id`	string	app_123
`items[].capabilities`	string[]	[2 shown]
`items[].status`	string	active
`next_cursor`	string \| null	null

Response example

Example response

200 OK
Content-Type: application/json

{
  "items": [
    {
      "id": "grant_123",
      "folder_id": "folder_123",
      "integration_id": "app_123",
      "capabilities": [
        "read",
        "write"
      ],
      "status": "active"
    }
  ],
  "next_cursor": null
}

How it works

Creating a grant belongs to an explicit interactive consent flow, not an unscoped service-token API. This endpoint must not reveal unrelated account grants to an integration.