Neon API (unofficial showcase)
DELETE/projects/{project_id}/jwks/{jwks_id}

Delete JWKS URL

Removes the specified JWKS URL from the project. JWTs signed by keys from the removed URL can no longer authenticate to the project's endpoints.

2 parameters
project_idstringrequired
The Neon project ID
jwks_idstringrequired
The JWKS ID

2 status codes
200Deleted a JWKS URL from the project
idstringrequired
The JWKS configuration's ID.
project_idstringrequired
The Neon project ID. Returned as `id` from `GET /projects`.
branch_idstringoptional
The Neon branch ID. Returned as `id` from `GET /projects/{project_id}/branches`.
jwks_urlstringrequired
URL of the provider's JWKS endpoint used to verify JWTs.
provider_namestringrequired
The name of the authentication provider (e.g., Clerk, Stytch, Auth0)
created_atstringrequired
The date and time when the JWKS was created
updated_atstringrequired
The date and time when the JWKS was last modified
jwt_audiencestringoptional
Expected JWT `aud` claim value configured for this JWKS.
role_namesarray<string>optional
Database role names that are permitted to authenticate using this JWKS configuration.
defaultGeneral Error. The request may or may not be safe to retry, depending on the HTTP method, response status code, and whether a response was received. - If no response is returned from the API, a network error or timeout likely occurred. - In some cases, the request may have reached the server and been successfully processed, but the response failed to reach the client. As a result, retrying non-idempotent requests can lead to unintended results. The following HTTP methods are considered non-idempotent: `POST`, `PATCH`, `DELETE`, and `PUT`. Retrying these methods is generally **not safe**. The following methods are considered idempotent: `GET`, `HEAD`, and `OPTIONS`. Retrying these methods is **safe** in the event of a network error or timeout. Any request that returns a `503 Service Unavailable` response is always safe to retry. Any request that returns a `423 Locked` response is safe to retry. `423 Locked` indicates that the resource is temporarily locked, for example, due to another operation in progress.
request_idstringoptional
Unique identifier for the request, useful for debugging. You can set this value manually by including an `X-Request-ID` header in the request. If not provided, the value will be generated automatically.
codestringrequired
Machine-readable code classifying the error type. See `message` for a human-readable explanation.
Default:
messagestringrequired
Error message

Error handling

Any other status is an error: General Error.

The request may or may not be safe to retry, depending on the HTTP method, response status code, and whether a response was received.

  • If no response is returned from the API, a network error or timeout likely occurred.
  • In some cases, the request may have reached the server and been successfully processed, but the response failed to reach the client. As a result, retrying non-idempotent requests can lead to unintended results.

The following HTTP methods are considered non-idempotent: POST, PATCH, DELETE, and PUT. Retrying these methods is generally not safe. The following methods are considered idempotent: GET, HEAD, and OPTIONS. Retrying these methods is safe in the event of a network error or timeout.

Any request that returns a 503 Service Unavailable response is always safe to retry.

Any request that returns a 423 Locked response is safe to retry. 423 Locked indicates that the resource is temporarily locked, for example, due to another operation in progress.