Impala Hotel Booking API

Name: Impala Hotel Booking API API
Brand: Impala Hotel Booking API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceOrder ManagementapiKey, bearer10 EndpointsREST

For Agents

Search hotels, retrieve rate plans, and create or cancel hotel bookings. Useful for travel agents, booking workflows, and hotel commission flows.

Connect the Impala Hotel Booking API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Impala Hotel Booking API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Impala Hotel Booking API API.

Search hotels and retrieve detailed property content including amenities and imagery

Pull rate plans and availability calendars for individual hotels

Create new bookings with guest details and selected rate plan

Modify the booking contact on a confirmed reservation

GET STARTED

Start building with Impala Hotel Booking API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Impala Hotel Booking API, keeping it validated and agent-ready.

The Impala Hotel Booking API lets developers add room booking and hotel content to apps without integrating with each property directly. Across 10 endpoints it covers hotel listings, rate plans, booking creation, modification, and cancellation, with separate sandbox and production servers. Authentication uses an x-api-key header for hotel and booking calls, plus a bearer JWT for the payment authorisation flow. The API is positioned for travel marketplaces, OTAs, and embedded booking widgets.

Use Cases

Patterns agents use Impala Hotel Booking API API for, with concrete tasks.

★ OTA Booking Integration

Plug Impala into an online travel agency or marketplace to expose hotel inventory and accept bookings end-to-end. The API delivers hotel content, rates, and booking creation in two main calls, so a working booking flow can be live in hours rather than the weeks usually needed for direct hotel integrations.

Search hotels in Barcelona for check-in 2026-07-12 and check-out 2026-07-14, list the cheapest rate plan for each hotel, and create a booking for the top result for two adults.

Travel Concierge Agents

Power AI travel concierges that can answer hotel availability questions and confirm bookings on behalf of users. The agent calls the hotels and rate plans endpoints to compare options, then creates or cancels a booking through the bookings endpoints with full guest details.

Given a user's destination and dates, retrieve the top three hotels with available rates under 200 EUR per night and confirm a booking on user approval.

Hotel Portfolio Expansion

Travel apps that already sell flights or experiences can add hotel inventory by integrating Impala. The hotels and rate-plans endpoints provide marketing content and pricing in a single, normalised schema so the app does not need to negotiate channel manager integrations with each property.

Pull the full hotel list from the sandbox account and import each hotel's name, amenities, and base rate into a local catalogue table.

Booking Cancellation Automation via Jentic

Customer support agents triggered through Jentic can cancel an Impala booking without an operator opening the dashboard. The agent looks up a booking by id, confirms cancellation policy, and executes DELETE on the booking, returning the cancellation reference to the user.

Cancel booking id BKG-19283 and return the cancellation timestamp to the support ticket.

Key Endpoints

10 endpoints — the impala hotel booking api lets developers add room booking and hotel content to apps without integrating with each property directly.

METHOD

PATH

DESCRIPTION

GET

/hotels

List all hotels

GET

/hotels/{hotelId}

Retrieve a single hotel with content

GET

/hotels/{hotelId}/rate-plans

List rate plans for a hotel

POST

/bookings

Create a booking

GET

/bookings/{bookingId}

Retrieve a booking

PUT

/bookings/{bookingId}

Modify a booking

DELETE

/bookings/{bookingId}

Cancel a booking

GET

/hotels

List all hotels

GET

/hotels/{hotelId}

Retrieve a single hotel with content

GET

/hotels/{hotelId}/rate-plans

List rate plans for a hotel

POST

/bookings

Create a booking

GET

/bookings/{bookingId}

Retrieve a booking

PUT

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Impala API keys and payment JWTs are stored encrypted in the Jentic vault. Agents receive a scoped Jentic token and never see the raw x-api-key or bearer JWT.

Intent-based discovery

Agents search Jentic by intent such as 'create a hotel booking' or 'cancel hotel booking' and Jentic returns the matching Impala operations with their input schemas.

Time to first call

Direct Impala integration: 1-2 days for auth, hotel search, and booking error handling. Through Jentic: under an hour. Search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Impala Hotel Bookings API v2

Newer v2 API from Impala with a streamlined hotel and booking surface

Choose v2 for new builds; choose this v1 only when integrating with an existing v1 client or rate plan structure.

Alternative

Booking.com

Major OTA with a much broader hotel inventory and affiliate booking flow

Choose Booking.com when scale of inventory matters more than direct commission and white-label control.

Complementary

Amadeus Airport and City Search

Airport and city lookup to enrich destination input before searching Impala hotels

Use Amadeus to resolve a free-text city or IATA code into structured destination data, then pass coordinates to Impala for hotel search.

FAQs

Specific to using Impala Hotel Booking API API through Jentic.

What authentication does the Impala Hotel Booking API use?

The hotel and booking endpoints require an x-api-key header issued by Impala. The payment authorisation endpoint additionally requires a bearer JWT. Through Jentic, both credential types are stored in the encrypted vault and injected at execution time, so the agent never sees the raw API key.

Can I cancel a booking through the Impala Hotel Booking API?

Yes. Issue DELETE /bookings/{bookingId} with the booking id. The response confirms the cancellation; refund handling depends on the rate plan policy attached to the original booking.

What are the rate limits for the Impala Hotel Booking API?

Impala enforces per-key fair-use limits but the published spec does not declare them as hard numbers. The sandbox is forgiving for testing; production keys are throttled per account, so agents should back off on 429 responses.

How do I create a hotel booking through Jentic?

Search Jentic for 'create a hotel booking' to find the operation backed by POST /bookings on this API. Load the schema, supply hotelId, ratePlanId, guest details, and dates, then execute. Jentic injects the x-api-key and any payment JWT at runtime.

Does the Impala Hotel Booking API have a sandbox?

Yes. The sandbox base URL is https://sandbox.impala.travel/v1 and the production URL is https://api.impala.travel/v1. Both expose the same endpoints; the sandbox returns realistic test data so booking flows can be validated before going live.

Can I retrieve a rate calendar for a hotel?

Yes. Use GET /hotels/{hotelId}/rate-plans for the full set and GET /hotels/{hotelId}/rate-plans/{ratePlanId} for a specific plan. These endpoints are marked beta in the spec, so schema fields can change.