Skip to main content
The Reserve Logs API provides access to the complete history of reservation activities in the system. These logs track all reservation events and changes, ordered by initialization date. These endpoints require authentication via cookie-based JWT tokens.

Available Endpoints

List Logs

Retrieve all reservation logs from the system

Authentication

All reserve logs endpoints require authentication using a JWT token stored in the access_token cookie. The user must have appropriate role permissions to access these endpoints.

Common Fields

INIT_DATE
date
Initialization date of the reservation event
Additional log fields
various
The log entries contain additional fields from the log_reservation table, which may include reservation IDs, user information, action types, status changes, timestamps, and other audit trail data.

Use Cases

  • Audit reservation activities
  • Track reservation history
  • Monitor system usage
  • Generate compliance reports
  • Investigate reservation issues
  • Analyze reservation patterns over time

Build docs developers (and LLMs) love