List API key concurrency policy history
Generated from the checked-in source. Do not edit this reference by hand.
GET /api/v1/workspaces/{workspace}/keys/{key}/concurrency-limit/history
Scoped readers receive descending revisions shared across rotations. Use the last revision as the next page cursor. The server resolves the organization from the authorized workspace. Foreign or missing workspaces return 404. The compatibility route remains supported with identical payload, owner, revision and replay semantics.
Operation: listKeyConcurrencyLimitHistoryByWorkspace.
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 GET "$NIU_ORIGIN/api/v1/workspaces/{workspace}/keys/{key}/concurrency-limit/history" \ -H "Authorization: Bearer $NIU_BEARER_TOKEN"Parameters
Section titled “Parameters”workspace
Section titled “workspace”Location: path. Required.
{ "type": "string", "format": "uuid"}Location: path. Required.
{ "type": "string", "format": "uuid"}before_revision
Section titled “before_revision”Location: query. Optional.
{ "type": "integer", "minimum": 1}Location: query. Optional.
{ "type": "integer", "minimum": 1, "maximum": 100, "default": 50}Request body
Section titled “Request body”No request body is declared.
Responses
Section titled “Responses”HTTP 200
Section titled “HTTP 200”Immutable policy history; no internal actor identifiers.
Content type: application/json.
{ "type": "object", "required": [ "data" ], "properties": { "data": { "type": "array", "items": { "type": "object", "required": [ "max_concurrent_requests", "revision", "recorded_at", "actor_kind", "actor_name" ], "properties": { "max_concurrent_requests": { "type": [ "integer", "null" ], "minimum": 0, "maximum": 10000, "description": "Maximum unresolved dispatched requests; null is unlimited and zero denies dispatch." }, "revision": { "type": "string", "pattern": "^[1-9][0-9]*$" }, "recorded_at": { "type": "string", "format": "date-time" }, "actor_kind": { "type": "string", "enum": [ "installation", "member" ] }, "actor_name": { "type": "string" } } } } }}HTTP 400
Section titled “HTTP 400”Invalid pagination
HTTP 401
Section titled “HTTP 401”Authentication required
HTTP 403
Section titled “HTTP 403”Insufficient management permission
HTTP 404
Section titled “HTTP 404”Workspace is outside operator scope, or key is absent from authorized workspace
Behavior and supported scope
Section titled “Behavior and supported scope”Scoped readers receive descending revisions shared across rotations. Use the last revision as the next page cursor. The server resolves the organization from the authorized workspace. Foreign or missing workspaces return 404. The compatibility route remains supported with identical payload, owner, revision and replay semantics.
Supported scope: implemented