canonical: https://jentic.com/apis/swaggerhub.fastpayhotels/fastpayhotels-booking-api-v2

# Fastpayhotels Booking API v2

Fastpayhotels Booking API is a specification designed for API integration customers in order to connect to Fastpayhotels Booking Engine System. Featuring multiple breaking changes into Booking API, v2 will reside in its own service URL, so customer can switch from v1 at their own rate As a rule, all URL for BookingAPI v2 are the same as legacy V1, just by adding v2 to URL address. Some API methods. The API exposes 10 endpoints.

## For AI agents

Programmatically retrieve the list of hotels filtered by dates., retrieve content information about a single hotel.. Covers 10 operations.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Retrieve the list of hotels filtered by dates.
- Return a list of cheaper prices for selected hotels.
- Perform a fast live check both on-site and on-line against supplier system (for
- Confirm real-time reservation.
- Monitor Fastpayhotels Booking API v2 operational status and events

## Use cases

### E-Commerce Operations

Use the Fastpayhotels Booking API v2 to perform e commerce operations programmatically. The API provides 10 endpoints covering core functionality including retrieve the list of hotels filtered by dates., retrieve content information about a single hotel., retrieve hotel mapping information..

Example prompt: Call POST `/hotel/list` to retrieve the list of hotels filtered by dates.

### Automated Catalogue Management

Automate catalogue operations by combining multiple Fastpayhotels Booking API v2 endpoints. Agents can retrieve content information about a single hotel. and then retrieve hotel mapping information. in a single workflow.

Example prompt: Call POST `/hotel/details` to retrieve content information about a single hotel., then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Fastpayhotels Booking API v2 endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'retrieve the list of hotels filtered by dates.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/hotel/list` | Retrieve the list of hotels filtered by dates. |
| POST | `/hotel/details` | Retrieve content information about a single hotel. |
| POST | `/hotel/catalogue` | Retrieve hotel mapping information. |
| POST | `/hotel/portfolio` | Retrieve the list of hotels filtered by dates. |
| POST | `/booking/search` | Return a list of cheaper prices for selected hotels. |
| POST | `/booking/livecheck` | Perform a fast live check both on-site and on-line against supplier system (for |
| POST | `/booking/book` | Confirm real-time reservation. |
| POST | `/booking/cancel` | Cancel reservations. |

## Key resources

- **Catalogue** — Everything about Hotel=> Hotel List, Catalogue Data, Hotel Detail Info
- **Availability** — Availability queries
- **Booking** — Real-time booking engine

## Why Jentic

- **Setup:** Wiring the Fastpayhotels Booking API by hand means standing up its virtual host, chained POST flow across hotel lookup, live check, book and cancel, and your own error and retry handling. Through Jentic you install once, import Fastpayhotels Booking API v2 from the API Directory, store the connection once, and your agent calls it.
- **Permission scoping:** This API sends every request as a POST with the target in the request body, so scope the agent to the operations it needs, such as hotel/list and booking/search. You choose the operations it may call, so state-changing ones like booking/book or booking/cancel are not included unless you add them.
- **Credential handling:** This API declares no authentication, so there is no secret to hand around; any connection settings are held once by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'find available hotels for these dates' or 'confirm a booking', and Jentic returns the matching Fastpayhotels Booking API v2 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Fastpayhotels Booking API v2 use?

The Fastpayhotels Booking API v2 uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I retrieve the list of hotels filtered by dates. with the Fastpayhotels Booking API v2?

Yes. Use the POST `/hotel/list` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Fastpayhotels Booking API v2?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I retrieve the list of hotels filtered by dates. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve the list of hotels filtered by dates.'. Jentic returns the matching Fastpayhotels Booking API v2 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Fastpayhotels Booking API v2 have?

The Fastpayhotels Booking API v2 exposes 10 endpoints covering catalogue, availability, booking operations.

### Can I limit what my agent is allowed to do with the Fastpayhotels Booking API v2?

Yes. Because Jentic One is self-hosted, you decide which of this API's operations your agent may call, so you can grant read-only lookups like POST `/hotel/list` and POST `/booking/search` while withholding the rest. Every request here is a POST with the target in the body, and state-changing operations such as POST `/booking/book` and POST `/booking/cancel` are only reachable if you add them to the agent's allowed set. Your own rules, held in your Jentic One instance, also govern which connection settings the agent may use.