Saltar al contenido principal

HOTEL DISTRIBUTION PLATFORM

One API to orchestrate availability, bookings, and cancellations at scale

Connect gives integration teams a consistent contract to search inventory, create bookings, simulate cancellation costs, execute cancellations, and reconcile operations end to end.

Test + ProductionShared auth headersUTC-0 date-time standardProblemDetails errors

Built for operational teams that need reliability, observability, and fast onboarding.

  • Sandbox-first rollout
  • End-to-end booking flow
  • Correlation-ready support

Predictable integration behavior from first request to support resolution

Connect is structured around stable contracts and operational visibility. Teams can integrate once, reuse the same authentication model across endpoints, and keep booking state synchronized across systems.

The API documentation includes request and response examples, playground execution, business error mapping, and endpoint-specific object schemas so your implementation remains deterministic.

A visual integration journey from search to reconciliation

As you scroll, each step appears in sequence to represent the operational path used by most channel integrations.

POST/availability/byhotel | /availability/bylocation

Availability Query

Start by searching inventory by hotel or location to collect bookable options and pricing context.

Open endpoint docs

availability-query.json

{ "stay": "2026-07-10/2026-07-14", "occupancy": "2 adults" }
POST/bookings/create

Booking Creation

Confirm a selected offer and create the reservation, storing returned locators for future operations.

Open endpoint docs

booking-creation.json

{ "hotelChainLocator": "...", "rooms": [{ "rateKey": "..." }] }
GET/bookings/cancel/simulate

Cancellation Simulation

Preview cancellation costs and business outcome before applying any irreversible state change.

Open endpoint docs

cancellation-simulation.json

{ "hotelChainLocator": "...", "simulated": true }
DELETE/bookings/cancel

Booking Cancellation

Execute final cancellation when business rules allow it, and persist cancellation result codes.

Open endpoint docs

booking-cancellation.json

{ "hotelChainLocator": "...", "simulated": false }
GET/bookings

Booking Retrieval

Retrieve booking data at any point for monitoring, support workflows, and reconciliation pipelines.

Open endpoint docs

booking-retrieval.json

{ "from": "2026-07-01", "to": "2026-07-31", "status": "Confirmed" }

Start in 3 steps

1

Configure environments and credentials

Begin in Test, confirm your `Username` and `Password` headers, and validate base URLs before integration.

2

Validate the booking flow end to end

Execute availability, creation, simulation, cancellation, and retrieval with real payload examples.

3

Go live with operational controls

Add logging with `CorrelationId`, apply retry strategy, and keep date-time handling standardized to UTC-0.

Need integration support?

Contact the support/integration channel assigned to your account. Sharing complete diagnostic context will significantly reduce response times.

  • Endpoint and HTTP method
  • Environment used (Test or Production)
  • Request timestamp in UTC-0
  • CorrelationId and sanitized payload samples