List binary-verify outcomes for a tenant
Changed onReturns a tenant-scoped reverse-chronological page of binary-verify outcomes recovered from the tenant audit stream. Filters narrow the page; values that fall outside the accepted enums return 400. The response envelope mirrors /api/v1/audit/events (items / next_cursor / returned) but each item carries the original BinaryVerifyEvent shape plus a server-side timestamp and endpoint label.
Auth: requires audit.read permission or admin role, plus tenant access enforced via X-Tenant-ID.
Request
- Base URL: http://localhost:8081
- URL: http://localhost:8081/api/v1/edge/binary-integrity/events
- Auth: one of:
- API key in header X-API-Key
- HTTP bearer
Query parameters
Tenant id whose audit stream should be read. Must match caller scope; defaults to the authenticated/header tenant.
Maximum number of events in the response page. Default 100; values above 200 are silently capped to 200 to bound the Redis fetch cost.
Opaque stream-id cursor returned as next_cursor from the previous page. Format <ms>-<seq>; empty next_cursor means end-of-stream.
Filter by outcome. Short forms ok / fail are accepted and normalized to the canonical binary-verify-ok / binary-verify-fail event types.
Filter by signing scheme.
Filter by the endpoint label captured at ingest time (operator-supplied; max 256 chars).
Headers
Tenant isolation header (required on all protected routes).
Response
Binary-verify events page
Changes
- info
endpoint added
- info