Skip to main content
POST

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

X-Request-Id
string

Optional client correlation id, up to 128 characters. It is not echoed: the response's X-Request-Id is always our own req_… id. We log your value with the request as client_request_id, so support can find a request by either id. A longer value is refused with 400 parameter_invalid.

Maximum string length: 128

Body

application/x-www-form-urlencoded

Form-encoded token request.

grant_type
string
required

authorization_code.

Allowed value: "authorization_code"
code
string
required

Code from the redirect. Single use; 60 seconds. Reuse revokes the grant.

redirect_uri
string<uri>
required

Same value as in the authorization request.

client_id
string
required

Client id.

Pattern: ^cli_[0-9A-HJKMNP-TV-Z]{26}$
code_verifier
string
required

PKCE verifier, 43–128 chars.

Required string length: 43 - 128
resource
string<uri>

RFC 8707; must match the authorization request.

Response

Tokens.

RFC 6749 §5.1 token response, plus PanoFlow extensions.

access_token
string
required

Opaque bearer token for resource. 15 minutes.

token_type
string
required

Always Bearer.

Allowed value: "Bearer"
expires_in
integer
required

Seconds; always 900.

refresh_token
string
required

New rotating refresh token, bound to the grant.

scope
string
required

Space-separated effective scopes.

grant_id
string

PanoFlow extension: the grant.

Pattern: ^grt_[0-9A-HJKMNP-TV-Z]{26}$
agent_id
string

PanoFlow extension: the agent the token acts as.

Pattern: ^agt_[0-9A-HJKMNP-TV-Z]{26}$