Set API key source policy
Generated from the checked-in source. Do not edit this reference by hand.
PUT /api/v1/workspaces/{workspace}/keys/{key}/ip-policy
Owner or installation administrator only. Rotation preserves this policy. Does not cancel already admitted requests. 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: setKeyIpPolicyByWorkspace.
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/workspaces/{workspace}/keys/{key}/ip-policy" \ -H "Authorization: Bearer $NIU_BEARER_TOKEN" \ -H 'Content-Type: application/json' \ --data @request.jsonParameters
Section titled “Parameters”workspace
Section titled “workspace”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": [ "allowed_cidrs", "expected_revision" ], "properties": { "allowed_cidrs": { "type": [ "array", "null" ], "maxItems": 64, "items": { "type": "string", "maxLength": 64 }, "description": "IPv4/IPv6 addresses or CIDRs, normalized to network CIDRs. Null permits all; empty denies all." }, "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.
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 network 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. 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