Revoke locally saved asset-management credentials
Generated from the checked-in source. Do not edit this reference by hand.
DELETE /api/v1/vendors/{id}/asset-management
Installation administrator only. The expected management revision must match the latest configuration. Revocation blocks internal reads through that revision. Optional erasure removes ciphertext from the active database only and requires confirm_erase=true; immutable metadata and audit events remain. Exact repeat requests do not duplicate audit events. This does not revoke Access Keys at Ark or erase backups, and does not affect inference bearer credentials.
Operation: revokeAssetManagement.
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.
[ { "adminBearerAuth": [] }]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 DELETE "$NIU_ORIGIN/api/v1/vendors/{id}/asset-management" \ -H "Authorization: Bearer $NIU_ADMIN_TOKEN" \ -H 'Content-Type: application/json' \ --data @request.jsonParameters
Section titled “Parameters”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": [ "expected_revision" ], "properties": { "expected_revision": { "type": "integer", "minimum": 1 }, "erase_history": { "type": "boolean", "default": false }, "confirm_erase": { "type": "boolean", "default": false } }}Responses
Section titled “Responses”HTTP 200
Section titled “HTTP 200”Local revocation applied. erased_revisions counts ciphertext rows erased by this call, and is zero on a repeat.
Content type: application/json.
{ "type": "object", "required": [ "data" ], "properties": { "data": { "type": "object", "required": [ "revision", "configured", "dispatch_available", "erased_revisions" ], "properties": { "revision": { "type": "integer", "minimum": 1 }, "configured": { "type": "boolean", "const": false }, "dispatch_available": { "type": "boolean", "const": false }, "erased_revisions": { "type": "integer", "minimum": 0 } } } }}HTTP 400
Section titled “HTTP 400”Invalid input or missing erasure confirmation.
HTTP 403
Section titled “HTTP 403”Installation administrator required.
HTTP 409
Section titled “HTTP 409”Missing configuration or stale revision.
HTTP 413
Section titled “HTTP 413”Request body exceeds 16 KiB.
Behavior and supported scope
Section titled “Behavior and supported scope”Installation administrator only. The expected management revision must match the latest configuration. Revocation blocks internal reads through that revision. Optional erasure removes ciphertext from the active database only and requires confirm_erase=true; immutable metadata and audit events remain. Exact repeat requests do not duplicate audit events. This does not revoke Access Keys at Ark or erase backups, and does not affect inference bearer credentials.