How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Descope Oauth2 API

The Oauth2 API from Descope — 30 operation(s) for oauth2.

Descope Oauth2 API is one of 16 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 42 operations across 30 paths, and defines 20 schemas. It is described by OpenAPI 3.0.3, at version 0.0.1.

Requests are made against 2 base URLs: https://api.descope.com, {customUrl}.

42 operations 30 paths 20 schemas 12 GET30 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
0.0.1
Base URL
https://api.descope.com
Authentication
HTTP Bearer, HTTP Bearer, HTTP Bearer, HTTP Bearer, HTTP Bearer
Contact
Resource Areas
1

Authentication & Security 5

Descope Oauth2 API declares 5 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). 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.

Paths & Operations 42

Across 30 paths, the API surfaces 42 operations — 12 GET, 30 POST. Each is listed below with its method, path, parameters, and response codes.

Oauth2 42
GET
/oauth2/v1/apps/agentic/{project_id}/{mcp_server_id}/authorize
Third Party application authorization GET endpoint by MCP server ID
ThirdPartyApplicationAuthorizeGetByMcpServerID 19 params → 200
POST
/oauth2/v1/apps/agentic/{project_id}/{mcp_server_id}/authorize
Third Party application authorization POST endpoint by MCP server ID
ThirdPartyApplicationAuthorizePOSTByMcpServerID 2 params body → 200
POST
/oauth2/v1/apps/agentic/{project_id}/{mcp_server_id}/token
Third Party application token endpoint by MCP server ID
ThirdPartyApplicationTokenEndpointByMcpServerID 2 params body → 200
GET
/oauth2/v1/apps/authorize
Get Authorization Endpoint
ThirdPartyApplicationAuthorizeGet 19 params → 200
POST
/oauth2/v1/apps/authorize
Post Authorization Endpoint
ThirdPartyApplicationAuthorize body → 200
POST
/oauth2/v1/apps/bc-authorize
Third Party application CIBA backchannel authentication endpoint
ThirdPartyApplicationCIBAEndpoint body → 200
POST
/oauth2/v1/apps/device
Third Party application device endpoint
ThirdPartyApplicationDeviceEndpoint body → 200
POST
/oauth2/v1/apps/finish-authorize
Finish Authorization Endpoint
ThirdPartyApplicationFinish body → 200
POST
/oauth2/v1/apps/revoke
OIDC revoke endpoint
ThirdPartyApplicationRevocationEndpoint body → 200
POST
/oauth2/v1/apps/token
Third Party application token endpoint
ThirdPartyApplicationTokenEndpoint body → 200
GET
/oauth2/v1/apps/userinfo
Third Party application Get UserInfo endpoint
ThirdPartyApplicationUserInfoEndpointGet 1 param → 200
POST
/oauth2/v1/apps/userinfo
Third Party application Post UserInfo endpoint
ThirdPartyApplicationUserInfoEndpointPost body → 200
GET
/oauth2/v1/apps/{project_id}/authorize
Third Party application authorization GET endpoint
ThirdPartyApplicationAuthorizeGetByProjectID 19 params → 200
POST
/oauth2/v1/apps/{project_id}/authorize
Third Party application authorization POST endpoint
ThirdPartyApplicationAuthorizePostByProjectID 1 param body → 200
POST
/oauth2/v1/apps/{project_id}/bc-authorize
Third Party application CIBA backchannel authentication endpoint
ThirdPartyApplicationCIBAEndpoint 1 param body → 200
POST
/oauth2/v1/apps/{project_id}/device
Third Party application device endpoint
ThirdPartyApplicationDeviceEndpoint 1 param body → 200
POST
/oauth2/v1/apps/{project_id}/revoke
Third Party application revoke endpoint by project ID
ThirdPartyApplicationRevocationEndpointByProjectID 1 param body → 200
POST
/oauth2/v1/apps/{project_id}/token
Third Party application token endpoint by project ID
ThirdPartyApplicationTokenEndpointByProjectID 1 param body → 200
GET
/oauth2/v1/apps/{project_id}/userinfo
Third Party application Get UserInfo endpoint by project ID
ThirdPartyApplicationUserInfoEndpointGetByProjectID 1 param → 200
POST
/oauth2/v1/apps/{project_id}/userinfo
Third Party application POST UserInfo endpoint by project ID
ThirdPartyApplicationUserInfoEndpointPostByProjectID 1 param body → 200
GET
/oauth2/v1/authorize
OIDC Authorize
OIDCAuthZEndpointGetStart 17 params → 200
POST
/oauth2/v1/authorize
OIDC Authorize
OIDCAuthZEndpointPostStart body → 200
POST
/oauth2/v1/authorize/entramfa
OIDC Authorize Entra MFA
OIDCAuthZEndpointEntraMFA body → 200
POST
/oauth2/v1/device
OIDC Device
OIDCDeviceEndpoint body → 200
GET
/oauth2/v1/finish-authorize
OIDC Finish Authorize
OIDCAuthZEndpointFinishPost 3 params → 200
POST
/oauth2/v1/finish-authorize
OIDC Finish Authorize
OIDCAuthZEndpointFinishGet body → 200
GET
/oauth2/v1/logout
OIDC End Session
OIDCEndSessionEndpointGet 5 params → 200
POST
/oauth2/v1/logout
OIDC End Session
OIDCEndSessionEndpointPost body → 200
POST
/oauth2/v1/revoke
OIDC Revoke
OIDCRevocationEndpoint body → 200
POST
/oauth2/v1/token
OIDC Token
OIDCTokenEndpoint body → 200
GET
/oauth2/v1/userinfo
OIDC UserInfo
OIDCUserInfoEndpointGet 1 param → 200
POST
/oauth2/v1/userinfo
OIDC UserInfo
OIDCUserInfoEndpointPost body → 200
GET
/{ssoAppId}/oauth2/v1/authorize
OIDC Authorize
OIDCSSOAppAuthZEndpointGetStart 17 params → 200
POST
/{ssoAppId}/oauth2/v1/authorize
OIDC Authorize
OIDCSSOAppAuthZEndpointPostStart 1 param body → 200
POST
/{ssoAppId}/oauth2/v1/authorize/entramfa
OIDC Authorize Entra MFA
OIDCSSOAppAuthZEndpointEntraMFA 1 param body → 200
POST
/{ssoAppId}/oauth2/v1/device
OIDC Device
OIDCDeviceEndpoint 1 param body → 200
GET
/{ssoAppId}/oauth2/v1/logout
OIDC End Session
OIDCSSOAppEndSessionEndpointGet 5 params → 200
POST
/{ssoAppId}/oauth2/v1/logout
OIDC End Session
OIDSSOAppCEndSessionEndpointPost 1 param body → 200
POST
/{ssoAppId}/oauth2/v1/revoke
OIDC Revoke
OIDCSSOAppRevocationEndpoint 1 param body → 200
POST
/{ssoAppId}/oauth2/v1/token
OIDC Token
OIDCSSOAppTokenEndpoint 1 param body → 200
GET
/{ssoAppId}/oauth2/v1/userinfo
OIDC UserInfo
OIDCSSOAppUserInfoEndpointGet 1 param → 200
POST
/{ssoAppId}/oauth2/v1/userinfo
OIDC UserInfo
OIDCSSOAppUserInfoEndpointPost 1 param body → 200

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are ThirdPartyApplicationTokenEndpointRequest (19 properties), ThirdPartyApplicationAuthZEndpointRequest (19 properties), OIDCAuthZEndpointRequest (17 properties), OIDCTokenEndpointRequest (16 properties). Each schema is shown below with its type and property counts.

ThirdPartyApplicationTokenEndpointRequest
object
19 properties
CIBAAuthRequest
object
9 properties
OperationResponse
object
OIDCUserInfoEndpointRequest
object
1 property
OIDCUserInfoEndpointResponse
object
1 property
OIDCDeviceEndpointRequest
object
6 properties
OIDCRevocationEndpointRequest
object
3 properties
OIDCEndSessionEndpointRequest
object
5 properties
ThirdPartyApplicationRevocationEndpointRequest
object
5 properties
OIDCAuthZEntraMFAEndpointRequest
object
10 properties
OIDCAuthZEndpointFinishRequest
object
3 properties
ThirdPartyApplicationAuthZEndpointRequest
object
19 properties
CIBAAuthResponse
object
3 properties
OIDCAuthZEndpointRequest
object
17 properties
ThirdPartyApplicationFinishEndpointRequest
object
4 properties
OIDCTokenEndpointRequest
object
16 properties
ThirdPartyApplicationUserInfoEndpointResponse
object
1 property
ThirdPartyApplicationUserInfoEndpointRequest
object
1 property
OIDCDeviceEndpointResponse
object
6 properties
OIDCTokenEndpointResponse
object
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

descope-oauth2-api-openapi.yml Raw ↑

Other APIs Descope publishes across the network.

Descope Apps API
Descope Auth API
Descope Custom Attributes API
Descope Default API
Descope Email API
Descope Embedded Link API
Descope Fedcm API
Descope Instant Message (IM) API
Descope Keys API
Descope Mgmt API
Descope Scim API
Descope Text Message (SMS) API
Where this information came from

This is an independent, third-party profile of Descope Oauth2 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.