Obtener permisos efectivos del token
Authentication
GET /v1/me
Returns the scopes of the authenticated Personal Access Token. Useful for verifying the token works and discovering which endpoints you can call.
GET
Obtener permisos efectivos del token
Returns the scopes of the authenticated token as stored in the database. Mostly useful for:
Response 204 — no body.
Equivalent to
- Validating at the start of your integration that the token is alive and carries the scopes you expect.
- Showing the end user (in your app’s settings UI) which actions they’ll be able to perform.
- Detecting whether the token has been revoked (the endpoint will return
401).
Endpoint
Headers
No body, query params, or path params required.
Example request
Response
200 OK
401 Unauthorized
Token is invalid, revoked, or expired. See Authentication errors.429 Too Many Requests
You hit the rate limit. See Rate limits.Common patterns
Validate at integration startup
Integration health check
CallGET /v1/me every 5 minutes as an internal liveness probe: if you get 401 repeatedly, alert your team that the token has been revoked or has expired.
Revoke the current token
DELETE /v1/me/token — server-side logout: marks the PAT this request is authenticated with as revoked. Future requests with the same token return 401.
keebai logout from the CLI: the local credentials file is removed and server-side the token is permanently invalid.
Typical use cases:
Logout in a multi-tenant integration
Your app lets a user unlink Keebai. You fire
DELETE /v1/me/token and delete the token from your storage.Rotation with guaranteed expiry
After minting a new token and rotating your integration, call
DELETE /v1/me/token on the old one to make sure it’s invalid (don’t wait for the user to revoke it manually).Authorizations
Personal Access Token con prefijo kbai_pk_. Generar desde el portal con permiso developer.manage_tokens.
Response
Permisos efectivos del token: intersección entre los scopes del token y los permisos actuales del usuario.
Example: