Database endpoints
Read the audit log
Read the newest entries in the tenant's tamper-evident audit log.
GET /v1/tenants/{tenant}/audit
- Choose an entry limitAsk for the recent audit records you need.
- Read actor and actionIdentify who acted and which target was affected.
- Keep the sequence numberLocate each event within the audit chain.
Before you start
Use your database bearer token.
Path parameters
| Field | Type | Required |
|---|---|---|
tenant | string | Required |
Query parameters
| Field | Type | Required |
|---|---|---|
limit | integer | Optional |
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. |
Read the result
entries contains recent audit records. Use actor, action and target to understand an event; seq identifies its place in the chain. Use the export endpoint when you need the full log.
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. |