Skip to main content
POST
Exchange a Pria API key for a JWT

Authorizations

x-api-key
string
header
required

Long-lived Pria API key (format pria_<40 hex chars>) used to obtain a JWT via POST /api/auth/api-key-signin. Only valid on the api-key-signin endpoint — every other admin/user endpoint expects the JWT issued by that exchange (sent as Authorization: Bearer <jwt> or x-access-token: <jwt>).

Headers

x-api-key
string
required

Pria API key (pria_ + 40 hex chars). Provisioned by an admin via the admin UI.

Pattern: ^pria_[0-9a-f]{40}$

Response

Key accepted — JWT and minimal profile returned.

token
string

JWT signed for the API-key-bound user. Use it in subsequent calls via Authorization: Bearer <token> or the x-access-token header. Token TTL matches the normal signin flow (6 hours by default, configurable via JWT_VALIDITY_SEC).

Example:

"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."

profile
object

Minimal profile envelope tailored for SDK / integration consumers. Smaller than the regular signin profile — see properties below.