Skip to main content

Audit Log Service

The Audit Log service keeps tamper-evident event journals for your customer. Each journal is opened by OpenHive for your customer and addressed by its namespace, a stable identifier such as entity-87-evt.

info

To activate the Audit Log service for your software, please contact us at https://openhive.eu/contact.

Available endpoints​

Every path lives under /v1/audit-log on the platform host (see Base URLs).

EndpointDescription
GET /v1/audit-log/journalsList your journals.
GET /v1/audit-log/journals/{namespace}Retrieve a single journal by its namespace.

See the API section for the full request and response reference of each endpoint.

What you can see​

Journals are scoped to your own customer: you only ever see your customer's journals, and only while they are not deleted.

  • A journal you cannot see — another customer's, or a deleted one — answers 404, never 403, so its existence is never disclosed.
  • The customerUid[] and exists[deletedAt] filters only narrow that list. Another customer's customerUid, or exists[deletedAt]=true, returns an empty list rather than an error.
curl "https://api.openhive.eu/v1/audit-log/journals" \
-H "Authorization: Bearer <access_token>"

curl "https://api.openhive.eu/v1/audit-log/journals/entity-87-evt" \
-H "Authorization: Bearer <access_token>"

Journals are read-only through the API: OpenHive creates and deletes them for you.

Authentication​

All endpoints require a bearer access token, passed in the Authorization header:

Authorization: Bearer <token>