Get current auth context
const url = 'https://api.dockt.com/v1/auth/me';const options = { method: 'GET', headers: {'x-dockt-expected-workspace': 'wsp_example', Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.dockt.com/v1/auth/me \ --header 'Authorization: Bearer <token>' \ --header 'x-dockt-expected-workspace: wsp_example'Returns the authenticated principal, active account or workspace scope, available scopes, and granted permissions.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Header Parameters
Section titled “Header Parameters”Rejects the request with 401 unless the browser session belongs to this auth_user_id. This assertion does not grant authority.
Unique Dockt workspace identifier.
Responses
Section titled “Responses”Envelope for a single resource response.
Envelope for a single resource response.
object
Current authorization context for the request, including principal type, active scope, available scopes, and permissions.
object
Account or workspace scope that a session can act within.
object
Whether the authenticated principal is acting at account level or within one workspace.
Unique Dockt account identifier.
Human-readable name shown in Dockt and customer systems.
Membership state for a user within an account.
Account or workspace scope that a session can act within.
object
Whether the authenticated principal is acting at account level or within one workspace.
Unique Dockt account identifier.
Human-readable name shown in Dockt and customer systems.
Membership state for a user within an account.
Signed-in user details for browser session requests.
object
Role used to authorize account and workspace actions.
Whether the authenticated principal is acting at account level or within one workspace.
ISO 8601 date-time string.
Example
{ "object": "single", "data": { "object": "auth_context", "auth_type": "session", "api_credential_type": "api_key", "principal_scope_type": "account", "permissions": [ "account:read" ], "active_scope": { "object": "principal_scope", "scope_type": "account", "scope_id": "acc_example", "account_id": "acc_example", "role": "owner", "status": "invited", "workspace_status": "active" }, "available_scopes": [ { "object": "principal_scope", "scope_type": "account", "scope_id": "acc_example", "account_id": "acc_example", "role": "owner", "status": "invited", "workspace_status": "active" } ], "actor": { "object": "session_actor", "role": "owner", "scope_type": "account", "scope_id": "acc_example" }, "updated_at": "2026-08-06T09:30:00Z" }}Problem Details response for HTTP 400. The type URI is the stable machine-readable error code.
Standard error response with a stable status, human-readable detail, and optional validation errors.
object
Structured request validation issues.
object
One request validation issue with a stable field path and human-readable message.
object
Example
{ "type": "https://docs.dockt.com/errors/invalid-request", "title": "Bad request", "status": 400, "detail": "The request did not match the expected schema.", "instance": "req_example1042"}Problem Details response for HTTP 401. The type URI is the stable machine-readable error code.
Standard error response with a stable status, human-readable detail, and optional validation errors.
object
Structured request validation issues.
object
One request validation issue with a stable field path and human-readable message.
object
Example
{ "type": "https://docs.dockt.com/errors/missing-auth", "title": "Unauthorized", "status": 401, "detail": "Send a valid bearer token or browser session.", "instance": "req_example1042"}Problem Details response for HTTP 403. The type URI is the stable machine-readable error code.
Standard error response with a stable status, human-readable detail, and optional validation errors.
object
Structured request validation issues.
object
One request validation issue with a stable field path and human-readable message.
object
Example
{ "type": "https://docs.dockt.com/errors/forbidden", "title": "Forbidden", "status": 403, "detail": "The authenticated principal does not have the required permission.", "instance": "req_example1042"}Problem Details response for HTTP 404. The type URI is the stable machine-readable error code.
Standard error response with a stable status, human-readable detail, and optional validation errors.
object
Structured request validation issues.
object
One request validation issue with a stable field path and human-readable message.
object
Example
{ "type": "https://docs.dockt.com/errors/not-found", "title": "Not found", "status": 404, "detail": "The requested resource was not found in the authenticated scope.", "instance": "req_example1042"}Problem Details response for HTTP 409. The type URI is the stable machine-readable error code.
Standard error response with a stable status, human-readable detail, and optional validation errors.
object
Structured request validation issues.
object
One request validation issue with a stable field path and human-readable message.
object
Example
{ "type": "https://docs.dockt.com/errors/conflict", "title": "Conflict", "status": 409, "detail": "The request conflicts with the current resource state.", "instance": "req_example1042"}Problem Details response for HTTP 422. The type URI is the stable machine-readable error code.
Standard error response with a stable status, human-readable detail, and optional validation errors.
object
Structured request validation issues.
object
One request validation issue with a stable field path and human-readable message.
object
Example
{ "type": "https://docs.dockt.com/errors/validation", "title": "Validation failed", "status": 422, "detail": "Correct the invalid fields and send the request again.", "instance": "req_example1042", "errors": { "issues": [ { "path": [ "body", "inputs", "3", "value" ], "message": "Expected a two-letter country code." } ] }}Problem Details response for HTTP 429. The type URI is the stable machine-readable error code.
Standard error response with a stable status, human-readable detail, and optional validation errors.
object
Structured request validation issues.
object
One request validation issue with a stable field path and human-readable message.
object
Example
{ "type": "https://docs.dockt.com/errors/rate-limit", "title": "Too many requests", "status": 429, "detail": "Wait for the Retry-After interval before retrying.", "instance": "req_example1042"}Problem Details response for HTTP 500. The type URI is the stable machine-readable error code.
Standard error response with a stable status, human-readable detail, and optional validation errors.
object
Structured request validation issues.
object
One request validation issue with a stable field path and human-readable message.
object
Example
{ "type": "https://docs.dockt.com/errors/internal", "title": "Internal server error", "status": 500, "detail": "Retry the request safely or contact Dockt support with the request ID.", "instance": "req_example1042"}Problem Details response for HTTP 503. The type URI is the stable machine-readable error code.
Standard error response with a stable status, human-readable detail, and optional validation errors.
object
Structured request validation issues.
object
One request validation issue with a stable field path and human-readable message.
object
Example
{ "instance": "req_example1042"}