Get the calling identity
const url = 'https://qinto-api.blotout.io/me';const options = {method: 'GET', headers: {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://qinto-api.blotout.io/me \ --header 'Authorization: Bearer <token>'Returns who is calling: the identity behind the presented token, the teams it may access, and the access it carries. Call it to confirm a credential works and to discover the teamId other operations need.
How it works
A team API token identifies only itself and its one team. A user-authorized OAuth token reports each team selected during consent. user is filled only when that grant includes the profile scope, and organizations when it includes profile, developer or bundles.
Required permissions
- None beyond a valid token;
useradditionally requires theprofilescope on the token’s grant, andorganizationstheprofile,developerorbundlesscope
Authorizations
Section titled “Authorizations”Responses
Section titled “Responses”The identity behind the presented token.
object
How the caller authenticated: a user-authorized OAuth token or a team API token.
For an OAuth token, the authorized app’s name; for a team API token, the token’s own name.
The authorizing user; null for team API tokens and for OAuth tokens granted without the profile scope.
object
Server-assigned unique id of the authorizing user.
Email address of the authorizing user.
First name, or null when never provided.
Last name, or null when never provided.
Every team this credential may access, with its independently granted scope.
A team this credential may access.
object
Server-assigned unique id of the team.
Display name of the team, or null when it has never been named.
When the team was created, as an ISO 8601 UTC timestamp.
The access granted specifically in this team.
Every developer organization the authorizing user belongs to; empty without the profile, developer or bundles scope and for team API tokens.
A developer organization the authorizing user belongs to.
object
Server-assigned unique id of the developer organization.
Display name of the developer organization.
The user’s role in the organization: owner, developer or member.
The presented token’s access as scope tokens: an OAuth token’s granted scope, or a team API token’s policies expressed as scopes.
Example
{ "tokenType": "oauth", "name": "Qinto CLI", "user": { "userId": "9c2f4b71-3d58-4a06-b1e2-7f40c8a5d312", "email": "dev@example.com", "firstName": "Ada", "lastName": "Lovelace" }, "teams": [ { "teamId": "7b8d1a52-6c1e-4b6f-9a30-2f8a54d1c3e9", "name": "Acme", "createdAt": "2026-06-18T00:00:00.000Z", "scopes": [ "team:write" ] } ], "organizations": [ { "organizationId": "5e8c2d90-4b17-4f3a-9d21-8a63f0b7c154", "name": "Acme Dev", "role": "owner" } ], "scopes": [ "team:write" ]}unauthenticated — The Authorization: Bearer token is missing, malformed, or no longer valid. Generate a team API token or obtain a new OAuth access token.
object
Machine-readable error slug; switch on this value rather than on the HTTP status alone.
Example
{ "error": "unauthenticated"}internal — Unexpected server error. Nothing is guaranteed to have been persisted; idempotent operations are safe to retry.
object
Machine-readable error slug; switch on this value rather than on the HTTP status alone.
Example
{ "error": "internal"}