Brave Partner Gateway

Brave Booking’s partner gateway lets every Brave company (incoming agency, hotel chain, hotel) sell its own hotel stock to its B2B partners — agencies, OTAs, wholesalers — through a single API, without Brave becoming a wholesaler.

Three gateways, one inventory

Each partner reaches the same catalogue and the same bookings through the gateway that matches its system:

• Brave gateway — clean REST, in JSON and XML (chosen by the Accept header), authenticated with X-Api-Key + X-Signature. This is the reference, documented page by page.
• OS-Travel compatible gateway (Octasoft) — JSON, POST {base}/api/hotel/<Method>, Credential { Login, Password } in every request, always HTTP 200 with ErrorMessage { Code, Description } on errors.
• Cyberesa compatible gateway — XML, form-url-encoded POST with a strRQ field, <Credential><Login/><Password/></Credential> as first child, d/m/Y dates, Available = 'Disponible'.

Key concepts

• {code} — the Brave company code (e.g. 1000) present in every Brave gateway URL.
• rateKey — signed offer key returned by search, to be replayed as-is in checkrate then in the booking.
• clientReference — your booking reference, mandatory and unique: a duplicate returns the same booking (idempotency).
• JSON / XML — the Brave gateway format is chosen by the Accept header (application/json by default, application/xml for XML).