Skip to main content
GET
Get the current user

Authorizations

DPoP
string
header
required

Per-request RFC 9449 DPoP proof signed with ES256. Protected requests use Authorization: DPoP your_access_token_here. Create a new proof for the exact method and normalized target URI, and include the server nonce when challenged.

Authorization
string
header
required

OAuth 2.0 with RFC 9700 security practices. Discover exact environment endpoints from /.well-known/openid-configuration and /.well-known/oauth-authorization-server, and discover the resource from /.well-known/oauth-protected-resource. Authorization-code clients use PKCE S256, the exact environment resource, nonce with openid, and DPoP binding. Confidential clients also require PAR and private_key_jwt. Access and refresh tokens are sender-constrained with DPoP. purchases:execute is unavailable and omitted from this scope registry.

Headers

X-Request-Id
string

Optional caller request identifier. Unsafe values are replaced with a generated UUID.

Pattern: ^[A-Za-z0-9._~-]{8,128}$

Response

The current safe user projection.

The current pairwise subject and safe display preferences without provider identity fields.

id
string
required

Pairwise subject identifier for the current resource owner and client.

Pattern: ^[A-Za-z0-9_-]{43}$
display_currency
string | null
required

Preferred display currency, or null when none is safely available.

Pattern: ^[A-Z]{3}$
display_mode
enum<string>
required

Whether amounts are displayed in the local currency or US dollars.

Available options:
local,
usd