Skip to main content

Reservations (Shared + Partner Surfaces)

Reservations are exposed through multiple APIs in LosCenotes.

Partner-specific reservation surfaces​

Public partner API​

  • GET /api/partner/reservations
  • GET /api/partner/reservations/:id
  • POST /api/partner/reservations
  • POST /api/partner/reservations/:id/cancel

Partner management reservations​

  • GET /api/partner-reservations
  • GET /api/partner-reservations/stats
  • GET /api/partner-reservations/:id
  • POST /api/partner-reservations
  • PATCH /api/partner-reservations/:id
  • POST /api/partner-reservations/:id/cancel

Shared reservation endpoints often used in integrations​

  • GET /api/public/reservations/:id?email=...&confirmationCode=...
  • GET /api/public/reservations/by-confirmation/:confirmationCode?email=...
  • POST /api/public/reservations/validate

Contract notes​

  • API responses expose monetary amounts in cents
  • list endpoints use the standard pagination wrapper
  • partner reservation management uses JWT/partner context, while the public partner API uses X-API-Key
  • public reservation lookup endpoints require query verification data such as email and optionally confirmationCode

Important correction​

Older drafts of this documentation described flows like confirmation, check-in, completion and bulk reservation endpoints under /partner/reservations. Those are not part of the current public partner controller surface and are intentionally omitted here.