Descope Auth API
The Auth API from Descope — 52 operation(s) for auth.
Descope Auth API is one of 15 APIs that Descope publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 68 operations across 62 paths, and defines 82 schemas. It is described by OpenAPI 3.2.0, at version 0.0.1.
Requests are made against 2 base URLs: https://api.descope.com, {customUrl}.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 10
Descope Auth API declares
10 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (Project ID) (Descope_Project_ID).
It accepts HTTP bearer tokens (Project ID:Refresh JWT) (Descope_Project_ID_Refresh_JWT).
It accepts HTTP bearer tokens (ProjectId:AccessKey) (Descope_Project_ID_Access_Key).
It accepts HTTP bearer tokens (Project ID:Session JWT) (Descope_Project_ID_Session_JWT).
It accepts HTTP bearer tokens (ProjectId:ManagementKey) (Descope_Project_ID_and_Management_Key).
It accepts HTTP bearer tokens (Project ID) (Descope Project ID).
It accepts HTTP bearer tokens (Project ID:Refresh JWT) (Descope Project ID:Refresh JWT).
It accepts HTTP bearer tokens (Project ID:Session JWT) (Descope Project ID:Session JWT).
It accepts HTTP bearer tokens (ProjectId:ManagementKey) (Descope Project ID and Management Key).
It accepts HTTP bearer tokens (ProjectId:AccessKey) (Descope Project ID:Access Key).
By default, every request must be authenticated.
Descope_Project_ID— Project ID as bearer token.Descope_Project_ID_Refresh_JWT— Project ID:Refresh JWT as bearer token.Descope_Project_ID_Access_Key— Project ID:Access Key as bearer token.Descope_Project_ID_Session_JWT— Project ID:Session JWT as bearer token.Descope_Project_ID_and_Management_Key— Project ID:Management Key as bearer token.Descope Project ID— Project ID as bearer token.Descope Project ID:Refresh JWT— Project ID:Refresh JWT as bearer token.Descope Project ID:Session JWT— Project ID:Session JWT as bearer token.Descope Project ID and Management Key— Project ID:Management Key as bearer token.Descope Project ID:Access Key— Project ID:Access Key as bearer token.
Paths & Operations 68
Across 62 paths, the API surfaces 68 operations — 12 GET, 56 POST. Each is listed below with its method, path, parameters, and response codes.
Schemas 82
The contract defines 82 schemas that model the data the API accepts and returns. The most detailed are ResponseUser (34 properties), JWTResponse (19 properties), OptionalJWTResponse (15 properties), UpdateUserNOTPRequest (11 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Descope 12
Other APIs Descope publishes across the network.
This is an independent, third-party profile of Descope Auth API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.