Ana içeriğe atla

​
Endpoint

POST /apiops/projects/{projectName}/jwks/parse-from-url

​
Authentication

Requires a Personal API Access Token. 
Authorization: Bearer YOUR_TOKEN

​
Request

​
Headers

HeaderValueRequired
AuthorizationBearer {token}Yes
Content-Typeapplication/jsonYes

​
Path Parameters

ParameterTypeRequiredDescription
projectNamestringYesProject name

​
Request Body

{
  "name": "my-jwk",
  "description": "JWK from URL",
  "url": "https://example.com/.well-known/jwks.json",
  "urlOptionConnectTimeout": 5000,
  "urlOptionReadTimeout": 10000,
  "urlOptionSizeLimit": 1048576,
  "kid": "key-id-1"
}
Note: If the URL returns a JWK Set (array of keys), use kid to specify which key to use from the array.

​
Request Body Fields

FieldTypeRequiredDescription
namestringYesJWK name (unique identifier)
descriptionstringNoJWK description
urlstringYesURL to fetch JWK from
urlOptionConnectTimeoutintegerNoConnection timeout in milliseconds (default: 5000)
urlOptionReadTimeoutintegerNoRead timeout in milliseconds (default: 10000)
urlOptionSizeLimitintegerNoMaximum response size in bytes (default: 1048576)
kidstringConditionalKey ID (kid) - Required when the URL returns a JWK Set (array of keys) to specify which key to use

​
Response

Same as Create JWK response format.

​
cURL Example

curl -X POST \
  "https://demo.apinizer.com/apiops/projects/MyProject/jwks/parse-from-url" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "my-jwk",
    "description": "JWK from URL",
    "url": "https://example.com/.well-known/jwks.json"
  }'

​
Permissions

User must have SECRETS + MANAGE permission in the project. For deployment operations (when deploying JWKs to environments), user must also have SECRETS + DEPLOY_UNDEPLOY permission.