Documented steps

Base URL https://api.clerk.com/v1 with header 'Authorization: Bearer <CLERK_SECRET_KEY>'; add 'Content-Type: application/json' on writes.
List sessions: GET /v1/sessions supplying user_id or client_id to scope the query. There is no documented unscoped 'all sessions' listing.
Optional query params: status (filter by session status), limit (greater than 0 and less than 501, default 10), offset (default 0).
The response is paginated: { data: Session[], total_count }.
Session status values are: abandoned, active, pending, ended, expired, removed, replaced, revoked.
Revoke a single session: POST /v1/sessions/{session_id}/revoke with no body. The response returns the Session with status 'revoked'.
To sign a user out everywhere, list their sessions filtered to status=active and revoke each session id returned.
SDK equivalents: clerkClient.sessions.getSessionList({ userId, status }) and clerkClient.sessions.revokeSession(sessionId).
Docs: https://clerk.com/docs/reference/backend/sessions/get-session-list and https://clerk.com/docs/reference/backend/sessions/revoke-session

Known gotchas

Revocation takes effect at the next token refresh, not instantly. An already-issued session JWT stays cryptographically valid until it expires (60 second default lifetime), so a revoked user can retain access for up to that window unless you also check session state server-side.
limit is capped below 501 and defaults to 10, so a user with many sessions will silently be truncated if you do not paginate.
The status values are easy to conflate: 'ended' means the user signed out but the session remains on the Client, 'removed' means signed out and removed from the Client, 'revoked' means the application terminated it server-side.
Listing requires user_id or client_id. A bare GET /v1/sessions is not a documented way to enumerate an instance.
Instance rate limits apply: 1000 req/10s production, 100 req/10s development. Revoking every session for a large tenant needs throttling.

clerk.com · 9 steps · unrated

List, search, filter and count Clerk users via GET /v1/users and GET /v1/users/count

clerk.com · 10 steps · unrated

Give your agent this knowledge — and 15,600+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

List, filter and revoke Clerk sessions via the Backend API (GET /v1/sessions, POST /v1/sessions/{id}/revoke)

Documented steps

Known gotchas

Related routes

Give your agent this knowledge — and 15,600+ more routes

Need this verified for your stack — or a route we don't have yet?