Descope REST API
- URL
-
https://api.descope.com - Spec
- https://docs.descope.com/examples/Descope_API.yaml
- Docs
- https://docs.descope.com/api
Authorization: Bearer <credential> Open Project Settings in the Descope Console and copy your Project ID. Descope's API docs state that sign-up/sign-in endpoints use Authorization: Bearer <ProjectID>.
Authorization: Bearer <credential> Obtain a user's refresh JWT by completing a Descope authentication flow such as the OTP flow described in One-Time-Password APIs. For user-scoped endpoints, Descope documents the header format as Authorization: Bearer <ProjectID>:<RefreshJWT>, so this credential is the combination of your project identifier and the user's refresh token.
Authorization: Bearer <credential> In the Descope Console, go to Company Settings → Management Keys and generate a management key for your project. The REST docs say management endpoints use a management key, and the CLI docs require setting it in DESCOPE_MANAGEMENT_KEY.
Authorization: Bearer <credential> Create an access key in the Descope Console from the Access Keys page, or via the descope access-key create command documented in descope CLI. Descope's API docs say management endpoints may use an access key.