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

# Fastpayhotels Booking API

Fastpayhotels Booking API is a specification designed for API integration customers in order to connect to Fastpayhotels Booking Engine System. **What's new in 1.9.3 version?** - **Availability in local currency** - Customers can now see hotel availability and book in the local currency of the hotel. (Previous authorisation is required) - See #/definitions/options - **Payment details** - Customer . 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 communications, crm, or developer tools - use for payments only.

## Capabilities

- Retrieve the list of hotels filtered by dates.
- Check availability from search parameters.
- Confirm real-time reservation.
- Query and filter Fastpayhotels Booking API records by parameters
- Monitor Fastpayhotels Booking API operational status and events

## Use cases

### Payments Operations

Use the Fastpayhotels Booking API to perform payments 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 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 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/availability` | Check availability from search parameters. |
| POST | `/booking/prebook` | Check availability about a product. Can check availability using avilability tok |
| 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 coding each hotel search, availability check, and booking request against its host and handling responses yourself. Through Jentic you install once, import the Fastpayhotels Booking API from the API Directory, and your agent calls it with no credential to manage.
- **Permission scoping:** The Fastpayhotels Booking API carries its targets in the request body across the hotel and booking operations, so scope your agent to the operations it needs, such as listing hotels and checking availability: you choose the operations it may call, so booking and cancellation are not included unless you add them.
- **Credential handling:** This API needs no credential, so there is nothing to store; if that changes, any credential would be stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list hotels filtered by dates' or 'check booking availability', and Jentic returns the matching Fastpayhotels Booking API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

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

The Fastpayhotels Booking API 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?

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?

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 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

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

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

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

Yes. Because you run Jentic One yourself, you decide which of this API's operations your agent may call, and it can only use the ones you allow. This API carries its targets in the request body across the hotel and booking operations, so you can scope an agent to read-only work like POST `/hotel/list` and POST `/booking/availability` while leaving out POST `/booking/book` and POST `/booking/cancel.` Booking and cancellation are only available to the agent if you explicitly add them to its allowed operations.