Get Current User

Resolves an access token to the user it was issued to. This is the quickest way to confirm a token works and to see exactly what it is allowed to do.

Endpoint

GET /v2/users/user-info

Authentication

This endpoint requires an OAuth access token. Send it as a bearer token:

Authorization: Bearer your_access_token

Required scope: users:read

Request Example

curl https://platform.chamelio.ai/v2/users/user-info \
  -H "Authorization: Bearer your_access_token"

import requests

url = "https://platform.chamelio.ai/v2/users/user-info"
headers = {
    "Authorization": "Bearer your_access_token"
}

response = requests.get(url, headers=headers)
print(response.json())

const response = await fetch('https://platform.chamelio.ai/v2/users/user-info', {
  method: 'GET',
  headers: {
    'Authorization': 'Bearer your_access_token'
  }
});

const data = await response.json();
console.log(data);

Response

Success Response

Status Code: 200 OK

{
  "user_id": 1001,
  "email": "john.doe@example.com",
  "first_name": "John",
  "last_name": "Doe",
  "role": "editor",
  "org_id": 123,
  "scopes": ["tasks:read", "tasks:write", "users:read"],
  "application_id": 42
}

Response Fields

Field	Type	Description
`user_id`	integer	Unique identifier of the user the token acts as
`email`	string	Email address of the user
`first_name`	string	First name of the user
`last_name`	string	Last name of the user
`role`	string	Organization role. One of `admin`, `editor`, `member`, `viewer`
`org_id`	integer	Organization the token is bound to
`scopes`	array of strings	Scopes granted to this token
`application_id`	integer or null	The OAuth application the token was issued to

Error Responses

400 Bad Request

Returned when the access token has no user behind it. client_credentials tokens act as the admin who created the application, so this applies only to tokens issued before application creators were recorded.

{
  "detail": "client_credentials tokens are not associated with a user"
}

401 Unauthorized

Returned when the access token is missing, unknown, revoked, or expired, or when an X-API-Key was sent instead of a bearer token. See OAuth error responses.

{
  "detail": "Invalid access token"
}

403 Forbidden

Returned when the token does not carry the required scope.

{
  "detail": "Insufficient scope; this endpoint requires: users:read"
}

404 Not Found

Returned when the token’s user no longer exists in the organization.

{
  "detail": "User not found"
}

429 Too Many Requests

Returned when your organization exceeds its per-minute request limit.

{
  "detail": "Rate limit exceeded"
}

Notes

This endpoint exists only on the OAuth surface. There is no API-key equivalent, because an API key is not tied to a specific end user.

Read scopes from the response rather than tracking what you requested. It reflects what the user actually approved, which may be narrower.

Cache the result for the life of a session. The values change only if the token is reissued.

Use Cases

Token verification - Confirm a freshly issued token works before making real calls
Capability discovery - Enable or hide features in your UI based on the granted scopes
User identification - Display who your integration is acting as
Debugging permissions - Explain a 403 by checking the token’s user and scopes

Overview

API Key Access

OAuth App Access

Webhooks

Endpoint

Authentication

Request Example

Response

Success Response

Response Fields

Error Responses

400 Bad Request

401 Unauthorized

403 Forbidden

404 Not Found

429 Too Many Requests

Notes

Use Cases

​Endpoint

​Authentication

​Request Example

​Response

​Success Response

​Response Fields

​Error Responses

​400 Bad Request

​401 Unauthorized

​403 Forbidden

​404 Not Found

​429 Too Many Requests

​Notes

​Use Cases

Endpoint

Authentication

Request Example

Response

Success Response

Response Fields

Error Responses

400 Bad Request

401 Unauthorized

403 Forbidden

404 Not Found

429 Too Many Requests

Notes

Use Cases