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

Auth0 keys API

The keys API from Auth0 — 9 operation(s) for keys.

Auth0 keys API is one of 76 APIs that Auth0 publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Keys. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and an AsyncAPI specification.

This API exposes 14 operations across 9 paths, and defines 27 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://{tenantDomain}/api/v2.

14 operations 9 paths 27 schemas 2 DELETE5 GET5 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://your-tenant.auth0.com/api/v2
Authentication
HTTP Bearer, OAuth 2.0
Terms of Service
Resource Areas
1

Authentication & Security 2

Auth0 keys API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (jwt) (bearerAuth). It supports OAuth 2.0 (oAuth2ClientCredentials) using the clientCredentials flow, exposing 221 scopes. By default, every request must be authenticated.

Paths & Operations 14

Across 9 paths, the API surfaces 14 operations — 2 DELETE, 5 GET, 5 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

keys 14
GET
/keys/custom-signing
Get Custom Signing Keys
get_custom_signing_keys → 200401403404429
DELETE
/keys/custom-signing
Delete Custom Signing Keys
delete_custom_signing_keys → 204401403429
PUT
/keys/custom-signing
Create or Replace Custom Signing Keys
put_custom_signing_keys body → 200400401403429
GET
/keys/encryption
Get All Encryption Keys
get_encryption_keys 3 params → 200400401403429
POST
/keys/encryption
Create the New Encryption Key
post_encryption body → 201400401403409429
POST
/keys/encryption/rekey
Rekey the Key Hierarchy
post_encryption_rekey → 204401403429
GET
/keys/encryption/{kid}
Get the Encryption Key by Its Key Id
get_encryption_key 1 param → 200400401403404429
DELETE
/keys/encryption/{kid}
Delete the Encryption Key by Its Key Id
delete_encryption_key 1 param → 204400401403429
POST
/keys/encryption/{kid}
Import the Encryption Key
post_encryption_key 1 param body → 201400401403409429
POST
/keys/encryption/{kid}/wrapping-key
Create the Public Wrapping Key
post_encryption_wrapping_key 1 param → 201400401403409429
GET
/keys/signing
Get All Application Signing Keys
get_signing_keys → 200400401403429
POST
/keys/signing/rotate
Rotate the Application Signing Key
post_signing_keys → 201401403429
GET
/keys/signing/{kid}
Get an Application Signing Key by Its Key Id
get_signing_key 1 param → 200400401403429
PUT
/keys/signing/{kid}/revoke
Revoke an Application Signing Key by Its Key Id
put_signing_keys 1 param → 200401403404429

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are CustomSigningKeyJWK (14 properties), GetSigningKeysResponseContent (12 properties), SigningKeys (12 properties), EncryptionKey (7 properties). Each schema is shown below with its type and property counts.

GetEncryptionKeyResponseContent
object
Encryption key
7 properties 5 required
ImportEncryptionKeyResponseContent
object
Encryption key
7 properties 5 required
CustomSigningKeyUseEnum
string
Key use
CustomSigningKeyCurveEnum
string
Curve
CustomSigningKeyJWK
object
JWK representing a custom public signing key.
14 properties 1 required
EncryptionKeyPublicWrappingAlgorithm
string
Encryption algorithm that shall be used to wrap your key material
ListEncryptionKeysResponseContent
ImportEncryptionKeyRequestContent
object
1 property 1 required
CreateEncryptionKeyResponseContent
object
Encryption key
7 properties 5 required
CreateEncryptionKeyPublicWrappingResponseContent
object
2 properties 2 required
CustomSigningKeyAlgorithmEnum
string
Key algorithm
GetCustomSigningKeysResponseContent
object
JWKS representing an array of custom public signing keys.
1 property
SigningKeys
object
12 properties 4 required
SetCustomSigningKeysResponseContent
object
JWKS representing an array of custom public signing keys.
1 property
CreateEncryptionKeyType
string
Type of the encryption key to be created.
EncryptionKeyState
string
Key state
EncryptionKeyType
string
Key type
SigningKeysDate
RotateSigningKeysResponseContent
object
2 properties 2 required
EncryptionKey
object
Encryption key
7 properties 5 required
GetSigningKeysResponseContent
object
12 properties 4 required
RevokedSigningKeysResponseContent
object
2 properties 2 required
CreateEncryptionKeyRequestContent
object
1 property 1 required
SetCustomSigningKeysRequestContent
object
JWKS representing an array of custom public signing keys.
1 property 1 required
CustomSigningKeyOperationEnum
string
ListEncryptionKeyOffsetPaginatedResponseContent
object
4 properties
CustomSigningKeyTypeEnum
string
Key type

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

auth0-keys-api-openapi.yml Raw ↑

Other APIs Auth0 publishes across the network.

Auth0 My Account API
Auth0 My Organization API
Auth0 for AI Agents
Auth0 actions API
Auth0 anomaly API
Auth0 Assertions API
Auth0 attack-protection API
Auth0 Authorization Models API
Auth0 Authorize User API
Auth0 AuthZenService API
Auth0 branding API
Auth0 client-grants API
Where this information came from

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