Skip to main content

Partner API Overview

This overview reflects the real controller structure currently implemented in LosCenotes API.

Base URL

https://service-gateway.loscenotes.com/api

All routes shown in this documentation already include the global /api prefix.

Partner endpoint families

FamilyBase pathAuthEndpoints
Public Partner API/api/partnerX-API-Key except seed-test-data7
Partner Registration/api/partnersPublic + throttling2
Partner Portal/api/partner-portalJWT partner user26
Admin Partners/api/admin/partnersJWT admin11
Settings/api/partner-settingsJWT partner user10
Users/api/partners/usersJWT + permissions9
Reports/api/partner-reportsJWT partner user7
Reservations/api/partner-reservationsJWT partner user6
Webhooks/api/partners/webhooksJWT + permissions4
Sandbox/api/partner-sandboxSandbox API key3
Webhook Simulator/api/partner/webhooks/simulatorSandbox API key4

Total current partner endpoints: 89

Response architecture

Partner endpoints follow the standard LosCenotes wrapper:

{
"success": true,
"message": "partners.portal.dashboard_retrieved",
"data": {},
"pagination": {
"total": 25,
"perPage": 15,
"currentPage": 1,
"lastPage": 2
},
"currency": {
"code": "MXN",
"symbol": "$"
}
}

Notes

  • pagination only appears on list endpoints
  • currency only appears on pricing-related endpoints
  • some endpoints return plain metadata objects in data, others return arrays or detail objects
  • the /api/partner family is mostly API-key protected, with POST /api/partner/seed-test-data as a public exception

Error shape

Error responses can include validation details like these:

{
"success": false,
"message": "validation.invalid_input",
"statusCode": 400,
"timestamp": "2026-03-10T18:00:00.000Z",
"path": "/api/partner/reservations",
"errors": {
"messages": ["guestEmail must be an email"],
"fields": {
"guestEmail": ["guestEmail must be an email"]
}
}
}

External integrations

New partner onboarding

Portal and operations

Shared platform APIs

Not every integration endpoint lives under src/partners. Partners also commonly use shared modules:

  • /api/pricing/*
  • /api/payment-methods*
  • /api/checkout/*
  • /api/public/discount-rules/*
  • /api/coupons/*
  • /api/cenotes/*

Those are documented in the shared platform section of this docs site.


Verified against controllers on 2026-03-10.