/v1/mgmt/user/passkeys/listAuthorization
Descope Project ID and Management Key Project ID:Management Key as bearer token.
In: header
Request Body
application/json
1 <= lengthList all passkeys for a user, using a valid management key.
curl -X POST "https://api.descope.com/v1/mgmt/user/passkeys/list" \ -H "Content-Type: application/json" \ -d '{ "loginId": "string" }'{ "passkeys": [ { "id": "string", "rpId": "string", "kind": "string", "displayName": "string", "createdTime": 0 } ]}export interface Response {passkeys?: UserPasskey[]}export interface UserPasskey {id?: stringrpId?: stringkind?: stringdisplayName?: stringcreatedTime?: number}List Logout Sessions Rules POST
List the project's active rules created by the logout sessions endpoint, with their ids, using a valid management key. Expired rules are not returned.
Logout Sessions Created in a Time Range POST
Log out every session in the project that was created inside a time range, using a valid management key. This is a project-wide rule: each matching session is logged out at its next refresh or validation, not immediately, and legitimate logins in the range are logged out too. The rule holds until it is deleted with the delete endpoint, or until it expires on its own one year after sessionsCreatedBefore; list the active rules with the list endpoint. A session refused at a refresh stays logged out after the rule is deleted or expires, and a user with many sessions in the range may be logged out of all their sessions. A range cannot cover time before the feature's rollout: sessionsCreatedAfter is clamped to it, the response shows the clamped value, and a range ending at or before it is rejected. Provide at least one of sessionsCreatedAfter and sessionsCreatedBefore as RFC 3339 times: sessionsCreatedAfter defaults to the beginning of time, and sessionsCreatedBefore defaults to now and cannot be in the future. sessionTypes limits the rule to sessions whose dtt claim matches one of its values exactly. No count of logged-out sessions is returned. To log out specific users, use the batch logout endpoint.