Me
Fetch the current authenticated user (useful as a health check after setting up auth).
The me object
The me object is a small summary of the authenticated user. It’s designed for “is my token valid?” checks and integration setup flows.
Properties
-
- Name
id- Type
- integer
- Description
- Unique identifier for the authenticated user.
-
- Name
email- Type
- string
- Description
- Email address for the authenticated user.
-
- Name
name- Type
- string
- Description
- Display name for the authenticated user.
-
- Name
is_admin- Type
- boolean
- Description
- Whether the user has admin access.
-
- Name
is_lister- Type
- boolean
- Description
- Whether the user is a lister (publishes listings).
-
- Name
plan- Type
- string
- Description
- Lister plan (
free,standard,pro).
GET/v1/me/
Fetch the current authenticated user
This endpoint is the fastest way to validate your token. It returns a small user summary in me.
Required scope
Tokens must include read:me (OAuth tokens and API keys). Older API keys created before scopes were introduced are treated as full-access keys until you rotate them.
Rate limits
Requests are rate limited. If you hit 429, back off and retry with a short delay (and jitter).
Request
GET
/v1/me/curl -s \
-H "Accept: application/json" \
-H "Authorization: Bearer YOUR_API_KEY" \
https://api.twentybaan.com/v1/me/Response
{
"ok": true,
"me": {
"id": 123,
"email": "you@example.com",
"name": "Your Name",
"is_admin": false,
"is_lister": true,
"plan": "standard"
}
}