Getting Started

The Axis Pro External API lets a booking engine, a partner site or an integrator
read a hotel's public catalogue and place reservations.

New here? Start with the Quickstart — five calls from an
API key to a confirmed booking, copy-pasteable.

What you need

An API key, issued by the hotel from their Axis Pro account. The key carries
three things that shape every call:

• An account. The key is the account — you never name one.
• A scope list. Each operation states the scope it needs.
• A property list. A key covering one property never sends X-Property; one
  covering several must send it on every property-bound call.

Conventions

• Money is a decimal string with two places ("450.00"), never a number.
  Parsing it as a float loses cents silently.
• Dates are YYYY-MM-DD. Timestamps are ISO-8601 with an offset.
• Collections page by cursor. There is no total and no page count.
• Errors carry error_code — match on that, never on message. Validation
  errors are the exception and carry no code; see Errors.
• POST /bookings requires an Idempotency-Key. See
  Idempotency.

Only what the hotel chose to expose

A room appears here only if it is published, sellable, and has an active rate
plan on the api sales channel. A room that sells perfectly well on the
hotel's own screens can be absent from this API — that is the hotel's decision,
and the first thing to check when rooms you expect are missing.

Pick the right environment

The server selector above offers sandbox and production, and the panel
below sends real requests to whichever is selected.

An API key belongs to exactly one environment. A sandbox key is refused by
production, and a production key is refused by the sandbox — both with the same
401 APIKEY_INVALID. So if a key you believe in is rejected, check the selected
server before anything else.

A booking created against production is a real booking in a real hotel. It
appears on the front desk's calendar and occupies the room. Explore on the
sandbox.