What Hrizn logs
Logging is for platform operations and support. Integrators do not receive a self-service API request history export today.
- HTTP method and route (parameterized patterns such as
/public/content/{id}/html, not raw resource IDs in analytics) - Response status code and timing
- API key and site association
- Source IP and optional
X-Idempotency-Keywhen present
What is not logged as API audit rows
- Health checks (
GET /public/health) — unauthenticated liveness probe - Failed authentication at the edge (invalid or missing API key) — blocked before your integration reaches route handlers
Rate limits and errors
Every response includes rate limit headers (X-RateLimit-*). See Rate Limiting for handling 429 responses.
Application errors use the standard error envelope documented in Errors. When opening a support ticket, include:
- The HTTP status and
error.codefrom the response body - The
X-Request-Idheader when present - Timestamp (UTC) and route pattern (e.g.
GET /public/content/{id}/html)
