iam.audit-logs.verifyRecompute the hash chain and check the signed digests and the head
ok is false on a chain break (an edited, inserted or deleted row), a digest whose signature or hash does not match, or a head past the last row (a cut-off tail).
Request syntax
GET /iam/api/audit-logs/verifyQuery parameters
maxRowsOptionalstring
Entries to check before stopping, 1 to 2000000; default 200000
Constraints: /^\d+$/
Response
200 with ok, checkedRows, legacyRows, redactedRows, firstSeq, lastSeq, complete (false when maxRows stopped the walk), startsAtGenesis, chainBreak (null, or where the chain breaks), head, and digests { checked, failed, latest }.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow iam:GetAuditLogs on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud iam audit-logs verifycurl -X GET "https://console.platform-development.deutschecloud.app/iam/api/audit-logs/verify" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY"Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_iam_audit-logs_verify.