Can I search hotels by destination with this API?

Yes. GET /hotels accepts search parameters and returns a list of hotels. You can then call GET /hotels/{hotelId} to pull content, GET /hotels/{hotelId}/room-types for inventory, and GET /hotels/{hotelId}/rates for pricing.

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

The published spec does not state explicit rate limit numbers. Impala throttles per-account, so agents should monitor for 429 responses and back off, especially when running large search sweeps across multiple destinations.

How do I create a hotel booking through Jentic?

Search Jentic for 'create a hotel booking' to surface the operation backed by POST /bookings on this v2 API. Load the schema, pass hotelId, room type, guest details, and dates, then execute. Jentic injects the x-api-key at runtime.

How do I cancel a booking through this API?

Call POST /bookings/{bookingId}/cancel with the booking id. The response confirms cancellation; refund treatment is determined by the rate's cancellation policy at the time of booking.

Should I use v1 or v2 of the Impala booking surface?

Prefer v2 for new builds. It has a smaller, more uniform set of endpoints and uses a simple x-api-key flow. Use v1 only when maintaining an existing integration that depends on the v1 rate plan model.

Can I limit what my agent is allowed to do with the Impala Hotel Bookings API?

Yes. Because you run Jentic One yourself, your own rules decide which of the eight operations the agent can call, so you can allow hotel search, GET /hotels/{hotelId}/rates, and GET /bookings/{bookingId} while withholding POST /bookings/{bookingId}/cancel and POST /bookings until you explicitly add them. Since the hotel id and booking id sit in the URL path, a rule can pin the agent to a single hotel or a single booking rather than the whole account. Your Impala x-api-key stays stored by your own instance and is injected only at execution time, so the agent operates strictly within the scope you set.