Account

Overview

Returns the 9Pic account behind an OAuth access token and every organisation that account can access, with its role in each. Use the returned org_id values in org-scoped paths such as List Events. This endpoint accepts OAuth access tokens only. An X-API-Key is already scoped to a single organisation, so there is nothing to look up and the call returns 403.

Endpoint

GET /api/v1/ext/account

Required scope: events:read

Example Request

curl -i \
  -H "Authorization: Bearer <oauth_access_token>" \
  "https://api.9pic.ai/api/v1/ext/account"

import requests

response = requests.get(
    "https://api.9pic.ai/api/v1/ext/account",
    headers={"Authorization": "Bearer <oauth_access_token>"},
)
print(response.status_code, response.json())

const response = await fetch(
  "https://api.9pic.ai/api/v1/ext/account",
  { headers: { Authorization: "Bearer <oauth_access_token>" } }
);
console.log(response.status, await response.json());

Example Response

{
  "responseType": "success",
  "message": "Account fetched successfully",
  "data": {
    "account_label": "organiser@example.com",
    "scopes": ["analytics:read", "events:read", "events:write"],
    "organisations": [
      { "org_id": 903, "name": "City Marathon", "slug": "city-marathon", "role": "admin" },
      { "org_id": 911, "name": "Trail Series", "slug": "trail-series", "role": "user" }
    ]
  }
}

Organisations are sorted by name. Pending team invitations are not included until the user accepts them.

Response Models

The payload inside data (AccountData):

Field	Type	Description
`data.account_label`	string \| null	Email of the signed-in 9Pic account.
`data.scopes`	string[]	Scopes granted to this token, sorted.
`data.organisations`	AccountOrganisation[]	Organisations the account can access. Empty when it has none.

AccountOrganisation:

Field	Type	Description
`org_id`	number	Organisation ID to use in `/api/v1/ext/{org_id}/...` paths.
`name`	string \| null	Organisation name.
`slug`	string \| null	Organisation slug.
`role`	string	The account’s role in this organisation: `admin` or `user`.

Error Responses

Status	Meaning
`400`	Both `X-API-Key` and a bearer token were sent.
`401`	No credentials, or the bearer token is malformed, expired, or could not be verified.
`403`	Called with an `X-API-Key`, no 9Pic account is linked to the sign-in, the account is inactive, the `events:read` scope is missing, or the host is not approved.
`429`	Rate limit exceeded. Back off and retry.

See Errors for canonical descriptions and retry guidance.

Get Started

Events

Memories

Browse Photos

Search

Video

Downloads

Pipeline

Webhooks

Models

Overview

Endpoint

Example Request

Example Response

Response Models

Error Responses

​Overview

​Endpoint

​Example Request

​Example Response

​Response Models

​Error Responses

Overview

Endpoint

Example Request

Example Response

Response Models

Error Responses