Skip to main content
POST
Create a personal access token

Authorizations

Authorization
string
header
required

The session token qumod login obtains through the device flow (POST /v1/auth/device/token). It acts as the signed-in user, like a console session, and needs no CSRF token.

Body

application/json
name
string
required

A display name, at most 100 characters. Surrounding whitespace is trimmed.

Required string length: 1 - 100
Example:

"ci-deploy"

scopes
enum<string>[]
required

The scopes the token may use, at least one. * grants every scope the user's own roles allow. See Scopes and permissions.

Minimum array length: 1
Available options:
*,
project:read,
usage:read,
audit:read,
audit:admin,
iam:read,
iam:admin,
organization:admin,
billing:admin,
signing_keys:admin
Example:

Response

The token was created. Store value now; it cannot be retrieved again.

A personal access token's metadata. The token value is never included.

id
string<uuid>
required
Example:

"7d9f1b3e-5a7c-4e9b-b1d3-f5a7c9e1b3d5"

name
string
required
Example:

"ci-deploy"

scopes
string[]
required

The scopes the token holds. See Scopes and permissions.

Example:
created_at
string<date-time>
required
Example:

"2026-10-04T09:12:44Z"

expires_at
string<date-time>
required

30 days after creation.

Example:

"2026-11-03T09:12:44Z"

value
string
required

The token secret. Shown only in this response.

Example:

"qumo_pat_3c9e1a7f5b2d8e4a0f6c3b9d7e1a5c2f8d4b0e6a2c9f7d3b1e5a8c0f4b6d2e9a"