List portal sessions
List the end users holding a revocable session on a portal, with each end user’s sessions.
Unreleased and subject to change without notice.
A session is revocable until it expires or is revoked. That includes
sessions whose portal URL was created but not opened yet. Pass an end
user’s externalId to portal.revokeSession to end their sessions.
Required Permissions
Your root key must have one of:
portal.*.create_portal_session(for any portal in the workspace)portal.<portal_id>.create_portal_session(for a specific portal)
It also accepts unkey:v1:<workspace_id>:projects/<project_id>/portals/<portal_id>/sessions/*
with #read or #write. Reading the portal itself is not enough.
Without the permission this returns 404, not 403.
Authorizations
Unkey uses bearer tokens for authentication. Public integrations use root keys, while the dashboard proxy uses short-lived JWTs. To authenticate, include the token in the Authorization header of each request:
Root keys have specific permissions attached to them, controlling what operations they can perform. Legacy permissions use tuple strings like api.*.create_key; resource permissions use Unkey Resource Names plus actions, like unkey:v1:ws_123:keyspaces/*#create_key.
Security best practices:
- Keep root keys secure and never expose them in client-side code
- Use different root keys for different environments
- Rotate keys periodically, especially after team member departures
- Create keys with minimal necessary permissions following least privilege principle
- Monitor key usage with audit logs.
Body
Identifies a resource by either its unique ID or its slug. Accepts a prefixed ID (such as 'proj_' or 'app_') or a slug.
3 - 255^[a-zA-Z0-9_-]+$"proj_1234abcd"
Maximum number of end users to return per request.
1 <= x <= 100Pagination cursor from a previous response to fetch the next page.
Use when hasMore: true in the previous response.
"user_123"
Returns only end users whose externalId starts with this string.
Matching is case-sensitive, and % and _ match literally.
256"user_"
Response
One page of end users with revocable sessions.
Metadata object included in every API response. This provides context about the request and is essential for debugging, audit trails, and support inquiries. The requestId is particularly important when troubleshooting issues with the Unkey support team.
End users with revocable sessions, ordered by externalId.
100Pagination metadata for list endpoints. Provides information necessary to traverse through large result sets efficiently using cursor-based pagination.