Who am I

Returns who you are, the one account your requests read, and what you may do there. Call it first: no other response repeats your permissions.

Response: { data } with principal (an API key, or a person signed in to our apps), account, permissions (one flat map that each API adds its permissions to) and extensions (the person's assigned extensions; empty for an API key).

Notes:

  • A permission is listed once the feature it allows exists. Ignore fields and permissions you do not know: new ones are added without notice.
  • A Scoped API key is answered with every Call History permission false.
  • HEAD answers the same status and headers with no body.
  • Every answer carries X-Request-Id and Cache-Control: private, no-store. A path under /me that names no endpoint answers 404 route_not_found.
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
uuid

The one account to answer about, by its id (account.id). Only a caller that may choose the account (EMAK support) sends it, and must; everyone else is answered about the account they belong to. Absent for a caller that must name it: 400 parameter_missing. Empty or not an account id: 400 parameter_invalid. Given twice: 400 parameter_invalid for any caller. Sent by a caller that reads its own account: 403 forbidden. An account that does not exist or is disabled: 404 reference_not_found. Each names account_id in param. A request that sends the legacy account header X-Tenant-Domain-Uuid is refused (400 parameter_unknown).

Responses

Language
Credentials
Bearer
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json