Set API key request rate policy
Generated from the checked-in source. Do not edit this reference by hand.
PUT /api/v1/organizations/{organization}/projects/{project}/keys/{key}/request-rate-limit
Owner or installation administrator only. Rotation preserves this policy. Does not cancel already admitted requests.
Operation: setKeyRequestRateLimit.
Authentication
Section titled “Authentication”Use the credential and permission scope described above. Each object below is an alternative; schemes within one object are required together.
[ { "bearerAuth": [] }]HTTP request
Section titled “HTTP request”Set NIU_ORIGIN to your installation origin (without /v1). Replace path, query and header placeholders with the required values. Query examples use curl 7.87 or newer to encode values with --url-query. Use the credential scope described above; a bearer token must have the authority required by this operation.
curl --fail-with-body -X PUT "$NIU_ORIGIN/api/v1/organizations/{organization}/projects/{project}/keys/{key}/request-rate-limit" \ -H "Authorization: Bearer $NIU_BEARER_TOKEN" \ -H 'Content-Type: application/json' \ --data @request.jsonParameters
Section titled “Parameters”organization
Section titled “organization”Location: path. Required.
{ "type": "string", "format": "uuid"}project
Section titled “project”Location: path. Required.
{ "type": "string", "format": "uuid"}Location: path. Required.
{ "type": "string", "format": "uuid"}Request body
Section titled “Request body”application/json
Section titled “application/json”Required.
{ "type": "object", "additionalProperties": false, "required": [ "requests_per_minute", "expected_revision" ], "properties": { "requests_per_minute": { "type": [ "integer", "null" ], "minimum": 0, "maximum": 1000000, "description": "Maximum dispatches per rolling 60 seconds; null is unlimited and zero denies dispatch." }, "expected_revision": { "type": "string", "pattern": "^[0-9]+$", "description": "Zero for initial configuration; maximum 9223372036854775806." } }}Responses
Section titled “Responses”HTTP 200
Section titled “HTTP 200”New policy and immutable history committed atomically. Rolling windows persist across revisions.
Content type: application/json.
{ "type": "object", "required": [ "data" ], "properties": { "data": { "type": "object", "required": [ "revision" ], "properties": { "revision": { "type": "string", "pattern": "^[1-9][0-9]*$" } } } }}HTTP 400
Section titled “HTTP 400”Invalid limit or revision
HTTP 401
Section titled “HTTP 401”Authentication required
HTTP 403
Section titled “HTTP 403”Owner permission required
HTTP 404
Section titled “HTTP 404”Workspace is outside operator scope, or key is absent from authorized workspace
HTTP 409
Section titled “HTTP 409”Stale policy revision
HTTP 422
Section titled “HTTP 422”Missing or invalid JSON fields
Behavior and supported scope
Section titled “Behavior and supported scope”Owner or installation administrator only. Rotation preserves this policy. Does not cancel already admitted requests.
Supported scope: implemented