The Sessions API exposes refresh-token sessions as a sub-resource of users. A session corresponds to a single refresh token row in theDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/JorLOrT/rappi2/llms.txt
Use this file to discover all available pages before exploring further.
tokens table. Users can always list and revoke their own sessions without any special permission. Accessing or revoking another user’s sessions requires the sesiones:read or sesiones:delete permission respectively.
GET /api/usuarios/me/sesiones
List the sessions belonging to the currently authenticated user. Authentication:Bearer token required.Permission required: none (own sessions only).
Query parameters
When
true, only non-revoked sessions that have not yet expired are returned. Set to false to include all historical sessions.Response — 200 OK
Returns an array ofTokenInfo objects ordered by fecha_expiracion descending.
Session (token row) ID.
ID of the user who owns this session.
ISO 8601 timestamp when the refresh token expires.
Whether the session has been explicitly revoked.
GET /api/usuarios//sesiones
List sessions for a specific user. The authenticated user may query their own sessions without extra permissions. Querying another user’s sessions requiressesiones:read.
Authentication: Bearer token required.Permission required: none for own sessions;
sesiones:read for other users.
Path parameters
ID of the user whose sessions to list.
Query parameters
Return only active (non-revoked, non-expired) sessions when
true.Number of records to skip for pagination.
Maximum number of records to return. Cannot exceed 200.
Response — 200 OK
Returns an array ofTokenInfo objects. See GET /api/usuarios/me/sesiones for the field list.
DELETE /api/usuarios//sesiones/
Revoke a single session by ID. The owner of the session can always revoke it. Revoking another user’s session requiressesiones:delete.
Authentication: Bearer token required.Permission required: none for own sessions;
sesiones:delete for other users.
Path parameters
ID of the user who owns the session.
ID of the session to revoke.
Response — 204 No Content
No response body is returned. If the session is already revoked the request is idempotent and still returns 204.DELETE /api/usuarios//sesiones
Revoke all active sessions for a user at once — a force-logout. The owner can revoke their own sessions. Revoking another user’s sessions requiressesiones:delete.
Authentication: Bearer token required.Permission required: none for own sessions;
sesiones:delete for other users.
Path parameters
ID of the user whose sessions to revoke.
Response — 200 OK
Number of sessions that were revoked by this request.
ID of the user whose sessions were revoked.