Requests

The Booking Engine API accepts JSON requests over HTTPS only. Calls over plain HTTP are rejected. Every request must be authenticated as described on the Authentication page.

​

Methods

The API follows REST conventions across the funnel:

​

Session identifier

Every call after session creation carries the sessionId in the path, for example /v2/{sessionId}/search/rooms. Create a session first with POST /v2/session, then reuse its identifier for the rest of the funnel.

​

Query parameters

Some GET endpoints take query parameters. The hotel and room searches support pagination through pageNumber and pageSize. Each endpoint’s Reference page lists the query parameters it accepts.

​

Headers

Several endpoints accept optional X-AVP-* headers to tune the response, such as the descriptions to expand or the picture templates to return. Each endpoint’s Reference page lists the headers it supports.

​

Idempotency

Read calls (GET) are safe to retry: they never change state. Calls that modify session or basket state (POST, PATCH, DELETE) are not idempotent. Retrying them can duplicate basket items or repeat an action, so retry these only when you know the previous call did not reach the server.