Get current user profile
GET/users/me
Retrieves the profile information for the currently authenticated user. This endpoint returns basic user details including name, email, and account status.
Use this endpoint to:
- Display user information in your application
- Verify the identity of the authenticated user
- Check user account status and permissions
The response includes the user's unique ID which can be used to reference the user in other API calls.
Two shapes, depending on the token:
- With
read:profile(orwrite:profile): the full profile shown in the example. - Any other user token: only the user's id and type,
{"data": {"id": "usr_...", "type": "user"}}, with noattributes. Use it to learn whose token you hold; it never includes the email, name, username or city.
A token with no user (a server-side client_credentials key, or an installation acting
as a company or syndicate) gets 403. Before this change a user token without
read:profile got 403 here too; code that read attributes unconditionally should
now check for it.
Responses
- 200
- 401
- 429
Successful response
Authentication required or token is invalid/expired. This error occurs when:
- No Authorization header is provided
- The access token is invalid or malformed
- The access token has expired
- The access token has been revoked
To resolve: Obtain a new access token using the OAuth 2.0 flow.
Too many requests in a short time period. The API enforces rate limits to ensure fair usage and system stability. When you exceed the limit, you'll receive this error along with headers indicating when you can retry.
Check the X-RateLimit-Reset header to know when your limit will reset.
Consider implementing exponential backoff in your application.
Response Headers
Request limit per hour
Remaining requests
UTC timestamp when the limit resets