OpenAPI map
Audience: Partner developer
Objective: Know which resource groups the Partner OpenAPI documents.
Spec entry points
| Resource | Location |
|---|---|
| OpenAPI JSON | GET /api/v1/openapi |
| Developers marketing/how-to | /developers |
| Reference UI | /developers/reference |
Partner tags (documented surface)
- System - health, openapi
- Availability -
/pms/availability - Reservations -
/pms/reservations - Guests -
/pms/guests - Catalog -
/items - API Keys - settings routes (session)
The full app also exposes a broader session API under /api/v1/* (CRM, F&B, HR, payroll, AI, …). Prefer the Partner OpenAPI for external integrations unless you have an explicit private integration agreement.