Verify the audit log

GET /v1/tenants/{tenant}/audit/verify

Check whether the audit chain is intactIntegrity does not determine whether an action was appropriate.

Select the audit logUse the tenant whose chain needs checking.
Verify linked hashesCheck the log's recorded sequence for damage.
Inspect the outcomeIf broken, read the first damaged sequence and detail.

Before you start

Use your database bearer token.

Path parameters

Field	Type	Required
`tenant`	`string`	Required

Headers

Field	Type	Required	Description
`x-oc-db-user`	`string`	Optional	Acting database user (role, grant and row-policy checks). Send with x-oc-db-key.
`x-oc-db-key`	`string`	Optional	API key of the x-oc-db-user user.

ok: true means this check found an intact hash chain. If it is false, inspect first_broken_seq and detail. Chain integrity does not itself tell you whether an audited action was authorized or appropriate.

Response statuses

HTTP status reference

Status	What to do
200	OK
400	Correct the request before retrying.
401	Check the credential and Authorization header.
402	Check feature access or available credits.
403	Check tenant access, roles and permissions.
429	Honor Retry-After when present; back off.
503	Honor Retry-After when present; check write outcomes.

Request example

curl --include --request GET "${OC_BASE_URL}/v1/tenants/${OC_TENANT}/audit/verify" \
  --header "Authorization: Bearer ${OC_TOKEN}"

Response example

Examples use synthetic values to show the response format.

Response status

{
  "ok": true,
  "entries": 3,
  "first_broken_seq": null,
  "detail": "Chain intact"
}

Illustrative integrity result; a broken chain can also return HTTP 200 with ok:false.

Download the OpenAPI specification for the complete response schemas.

Before you startCopy Anchor Link

Path parametersCopy Anchor Link

HeadersCopy Anchor Link

Read the resultCopy Anchor Link

Response statusesCopy Anchor Link

Before you start

Path parameters

Headers

Read the result

Response statuses