# liteAPI Documentation > Welcome to the Nuitee Connect Developer Documentation. This guide provides all the information you need to integrate Nuitee Connect and LiteAPI into your applications. Whether you are building a simple website or a complex booking system, our APIs offer flexible and powerful tools to meet your needs. Nuitee Connect is designed to be easy to use and highly efficient, ensuring that you can focus on building great features for your users. Our API provides seamless access to a wide range of hotel data, including availability, rates, and booking options, making it the perfect choice for travel and hospitality applications. Append .md to any documentation page URL to get its markdown version. ## Guides - [Overview](https://docs.liteapi.travel/docs/docs.md): High-level overview of Nuitee Connect — search, prebook, and book hotels from your app. - [FAQ](https://docs.liteapi.travel/docs/faq.md) - [Booking a Room](https://docs.liteapi.travel/docs/booking-a-room.md): This guide walks through booking a room using a sandbox API key. - [Step 1: Getting an API Key](https://docs.liteapi.travel/docs/getting-a-sandbox-key.md) - [Step 2: Requesting room rates](https://docs.liteapi.travel/docs/step-2-requesting-room-rates.md) - [Step 3: Pre-booking a room](https://docs.liteapi.travel/docs/step-3-pre-booking-a-room.md) - [Step 4: Booking a Room](https://docs.liteapi.travel/docs/step-4-booking-a-room.md) - [Searching for hotels](https://docs.liteapi.travel/docs/preparing-a-list-of-hotel-ids.md) - [Implementing a Payment Method](https://docs.liteapi.travel/docs/implementing-payment.md) - [1. User Payment (Nuitee SDK)](https://docs.liteapi.travel/docs/user-payment.md): Use Nuitee Connect's payment SDK to accept user payment - [Alternative - User payment with Stripe SDK](https://docs.liteapi.travel/docs/direct-stripe-integration-stripe-elements.md): Integrate Stripe Elements directly into your checkout to accept user payments for LiteAPI bookings, with full control over the payment UI. - [2. Account Credit Card](https://docs.liteapi.travel/docs/account-credit-card.md): Pay directly from the account’s credit card. - [3. Credit Line Payments](https://docs.liteapi.travel/docs/credit-line.md): This method is used when you have contracted a credit line - [Displaying Essential Hotel Details](https://docs.liteapi.travel/docs/displaying-hotel-details.md) - [Room Details](https://docs.liteapi.travel/docs/room-details.md) - [Hotel Reviews](https://docs.liteapi.travel/docs/hotel-reviews.md) - [Rate and Hotel Query Guide](https://docs.liteapi.travel/docs/rate-request-parameters-guide.md) - [Hotel Rates API JSON Data Structure](https://docs.liteapi.travel/docs/hotel-rates-api-json-data-structure.md) - [Adding guests during the booking step](https://docs.liteapi.travel/docs/adding-guests-during-the-booking-step.md) - [Canceling a Booking](https://docs.liteapi.travel/docs/canceling-a-booking.md) - [Getting Access to Flights](https://docs.liteapi.travel/docs/getting-access-to-flights.md): The Flights API allows you to search, price, and book flights through Nuitee Connect. - [Build a Flight Booking Experience](https://docs.liteapi.travel/docs/build-a-flight-booking-experience.md): Nuitee Connect aggregates real-time flight inventory from GDS, NDC, and LCC providers into a single API. - [Booking Flow Recipes](https://docs.liteapi.travel/docs/booking-flow-recipes.md): Practical implementation patterns for common flight booking scenarios using Nuitee Connect. - [Flight Booking Architecture](https://docs.liteapi.travel/docs/flight-booking-architecture.md): A practical reference for engineering teams building production flight booking systems on Nuitee Connect - [Flight Seat Map — Implementation Guide](https://docs.liteapi.travel/docs/flight-seat-map-implementation-guide.md): How the seat map works in the whitelabel frontend, from API data to rendered grid. Use this as a reference if you're building a seat map from the same data source. - [Flights — Support & Billing Model](https://docs.liteapi.travel/docs/flights-support-billing-model.md): How Nuitée services flight bookings, how airline changes reach your system, and how servicing costs settle. - [Whitelabel Booking Site](https://docs.liteapi.travel/docs/whitelabel-booking-site.md) - [Whitelabel Appearance](https://docs.liteapi.travel/docs/customizing-appearance.md): Configuring the Appearance of Your White Label Booking Site - [Whitelabel Configuration](https://docs.liteapi.travel/docs/configuring-your-liteapi-powered-white-label-booking-site.md): Configuring Your Nuitee Connect-Powered White Label Booking Site - [Deeplinking to Whitelabel](https://docs.liteapi.travel/docs/deeplinking-to-whitelabel.md): This guide explains how to use URL parameters to deep link to the Hotel Listing, Hotel Details, and Checkout pages with pre-filled data. It includes parameter descriptions, values, and examples for easy implementation. - [Single Sign-On Deep Link](https://docs.liteapi.travel/docs/single-sign-on-deep-link-guide.md): This guide explains how to integrate External Auth SSO into your whitelabel project. Your backend requests a one-time magic login link from our API using a signed payload. When the user is redirected to that link, they are instantly authenticated and sent to your chosen destination page. The document covers required setup, request/response formats, signature generation, common errors, testing steps, and a ready-to-use Postman collection. - [Password-Protected Site Access (`id` + `sig`)](https://docs.liteapi.travel/docs/password-protected-site-access-id-sig.md) - [Custom Domain Guide](https://docs.liteapi.travel/docs/custom-domain-guide.md): This guide walks you through the entire process of configuring your domain to point to your website hosted on our platform. - [Whitelabel - Loyalty Program](https://docs.liteapi.travel/docs/loyalty-program-1.md): Wire your existing loyalty and rewards program into the WhiteLabel hotel booking flow. Guests can earn points, see rewards, and track benefits during search and checkout. - [Loyalty Program - No Validation Required](https://docs.liteapi.travel/docs/loyalty-program-no-validation-required.md): This document covers the **No Validation Required** method in detail. For general loyalty program information, see the overview document. - [Loyalty Program - Membership Number Validation](https://docs.liteapi.travel/docs/loyalty-program-membership-number-validation.md): This document covers the **Membership Number Validation** method in detail. For general loyalty program information, see the overview document. - [Hotel Ranking & Sorting Logic](https://docs.liteapi.travel/docs/hotel-ranking-sorting-logic.md): The Nuitee Connect WhiteLabel interface sorts hotel search results using a **weighted scoring system** designed to balance price competitiveness, quality, location relevance, and popularity. This document explains how hotels are ranked, how individual factors are weighted, and how **Best Seller** hotels receive special treatment in the ranking process. - [External Checkout - Integration Guide](https://docs.liteapi.travel/docs/external-checkout-integration-guide.md) - [External Checkout — Dashboard Setup Guide](https://docs.liteapi.travel/docs/external-checkout-dashboard-setup-guide.md): Partner teams setting up External Checkout from the Nuitée partner dashboard - [External Checkout — Endpoint Reference](https://docs.liteapi.travel/docs/external-checkout-endpoint-reference.md): Partner engineering teams implementing the External Checkout integration - [Vouchers API Guide](https://docs.liteapi.travel/docs/vouchers-api-guide.md) - [Revenue Management and Commission](https://docs.liteapi.travel/docs/revenue-management-and-commission.md) - [Nuitee Managed (Dynamic) Pricing](https://docs.liteapi.travel/docs/nuitee-managed-dynamic-pricing.md): Let the market drive your prices - [Perks and Promotions](https://docs.liteapi.travel/docs/perks-and-promotions.md) - [GraphQL Overview](https://docs.liteapi.travel/docs/overview-graphql.md): Search rates, prebook, and book hotels with the Nuitee Connect GraphQL API. Request only the fields you need in one query. - [Getting Started](https://docs.liteapi.travel/docs/getting-started-3.md) - [1. Search offers (Rates search)](https://docs.liteapi.travel/docs/avail.md): This GraphQL query allows developers to retrieve detailed rate information for hotels, supporting multi-room bookings. By making a request with the required parameters, you receive an array of offers, each containing comprehensive rate details. - [2. Validate an offer (Prebook)](https://docs.liteapi.travel/docs/valuation.md): The **Valuation query** (also known as **Prebook**) is used to verify that a selected hotel rate is still available before proceeding with the booking. - [3. Book (Confirm a booking)](https://docs.liteapi.travel/docs/reservation.md): The Booking Mutation is the final step in the reservation process, where a confirmed booking is created using the Prebook ID. - [Building a Nuitee Connect app on Node.js](https://docs.liteapi.travel/docs/nodejs-cookbook.md) - [Integrate a Hotels List Widget](https://docs.liteapi.travel/docs/integrate-a-hotels-list-widget.md): In this tutorial, you will learn how to integrate and use the Nuitee Connect Hotels List Widget in your web application to display a dynamic, interactive list of hotels. Follow the steps below to get started. - [Integrate a Map Widget](https://docs.liteapi.travel/docs/integrate-a-map-widget.md): In this tutorial, you will learn how to integrate and use the Nuitee Connect Map Widget in your web application to display a dynamic, interactive map. Follow the steps below to get started. - [Integrate a Search Bar Widget](https://docs.liteapi.travel/docs/integrate-a-search-bar-widget.md): In this tutorial, you will learn how to integrate and use the Nuitee Connect Search Bar Widget in your web application to display a dynamic, interactive search bar. Follow the steps below to get started. - [Stream Hotel Rates](https://docs.liteapi.travel/docs/stream-hotel-rates.md) - [Weather Data API Endpoint](https://docs.liteapi.travel/docs/weather-data-api-endpoint.md) - [Add-ons: Adding Amenities to a Booking](https://docs.liteapi.travel/docs/attaching-add-ons-to-user-payment.md): Add Ons are amenities that can be added on to hotel bookings during the checkout process. - [Using Nuitee Connect webhooks](https://docs.liteapi.travel/docs/using-liteapi-webhooks.md) - [Security Overview](https://docs.liteapi.travel/docs/security-privacy-compliance-overview.md): Nuitee Connect is designed with security, privacy, and regulatory compliance as foundational principles. We understand that our customers operate in regulated environments and rely on Nuitee Connect to process sensitive business and booking-related data in a secure and compliant manner. - [Data Protection & Privacy](https://docs.liteapi.travel/docs/data-protection-privacy.md): Nuitee Connect is committed to protecting the confidentiality, integrity, and availability of data processed through its platform. This page describes how Nuitee Connect handles personal data and other sensitive information in accordance with applicable data protection regulations, including the EU General Data Protection Regulation (GDPR). - [Data Processing Agreement (DPA)](https://docs.liteapi.travel/docs/data-processing-agreement-dpa-europe.md): This page describes the data protection and processing commitments applicable to customers subject to European data protection laws, including the **EU General Data Protection Regulation (GDPR)**. Nuitee Connect offers a Data Processing Agreement (DPA) that governs the processing of personal data on behalf of customers using Nuitee Connect services. - [Regulatory Compliance](https://docs.liteapi.travel/docs/regulatory-compliance.md): Nuitee Connect is designed to operate in compliance with applicable legal and regulatory requirements related to data protection, payment security, and information security. This page outlines Nuitee Connect’s compliance posture and the regulatory frameworks most commonly referenced by customers. - [Data Encryption](https://docs.liteapi.travel/docs/data-encryption.md): Nuitee Connect uses industry-standard encryption mechanisms to protect data both in transit and at rest. Encryption is a core control to ensure the confidentiality and integrity of customer data processed through the platform. - [Authentication & Access Control](https://docs.liteapi.travel/docs/authentication-access-control.md): Nuitee Connect implements strict authentication and access control mechanisms to ensure that only authorized users and systems can access its APIs and internal systems. - [Infrastructure & Hosting Security](https://docs.liteapi.travel/docs/infrastructure-hosting-security.md): Nuitee Connect operates on secure, modern cloud infrastructure designed to ensure high availability, resilience, and strong security controls. Infrastructure security is a foundational component of Nuitee Connect’s overall security posture. - [Logging, Monitoring & Incident Response](https://docs.liteapi.travel/docs/logging-monitoring-incident-response.md): Nuitee Connect maintains logging, monitoring, and incident response processes designed to detect, respond to, and mitigate security and operational incidents in a timely manner. - [Vulnerability Management](https://docs.liteapi.travel/docs/vulnerability-management.md): Nuitee Connect maintains a vulnerability management program to identify, assess, and remediate security vulnerabilities in a timely manner. The goal is to reduce risk and continuously improve the security posture of the platform. - [Data Residency & International Data Transfers](https://docs.liteapi.travel/docs/data-residency-international-data-transfers.md): Nuitee Connect processes and stores data in accordance with applicable data protection laws, including requirements related to data residency and international data transfers. - [Business Continuity & Disaster Recovery](https://docs.liteapi.travel/docs/business-continuity-disaster-recovery.md): Nuitee Connect maintains business continuity and disaster recovery practices designed to ensure service availability, protect data, and support timely recovery in the event of system failures, incidents, or disasters. - [Performance, Reliability & Rate Limiting](https://docs.liteapi.travel/docs/performance-reliability-rate-limiting.md): Nuitee Connect is designed to provide reliable, predictable API performance at scale. This page describes Nuitee Connect’s performance characteristics, availability targets, rate limiting behavior, and observability features available to customers. - [Service Availability & Uptime Commitment](https://docs.liteapi.travel/docs/service-availability-uptime-commitment.md): Nuitee Connect is designed to provide a highly available and reliable service for travel search and booking operations. This page outlines Nuitee Connect’s service availability objectives, uptime commitment, and operational principles. - [MCP](https://docs.liteapi.travel/docs/mcp.md) ## API Reference - [Overview](https://docs.liteapi.travel/reference/overview.md): Go from zero to live hotel search and booking in hours. REST API, production-like sandbox, and clear docs — search, prebook, book. - [Simple Authentication](https://docs.liteapi.travel/reference/authentication.md): All requests to Nuitee Connect must be authenticated using an API key. You can find your API key in the Nuitee Connect dashboard. An account provides analytics and management for all bookings through the attached API keys. - [HMAC Authentication](https://docs.liteapi.travel/reference/secure-authorization.md): Nuitee Connect also provides a secure method for authenticating requests without directly transmitting your private API key. Instead, you can sign your request using HMAC SHA-512 and include the signature along with a public key in the request headers. This ensures better security by preventing your private key from being exposed in transit. - [Getting Started With Nuitee Connect](https://docs.liteapi.travel/reference/getting-started-1.md): Learn how to quickly get up and running with Nuitee Connect. Follow these steps to start making API calls in minutes. - [API Pricing & Usage Costs](https://docs.liteapi.travel/reference/api-pricing-usage-costs.md): Nuitee Connect follows a transparent, usage-based pricing model with **monthly billing cycles**. This page describes API request costs per endpoint category, as well as additional billable features available through the Nuitee Connect Dashboard. Unless otherwise specified in a commercial agreement, the pricing below applies to standard Nuitee Connect usage. - [Hotel Booking workflow](https://docs.liteapi.travel/reference/workflow.md): The Nuitee Connect product streamlines the process of fetching and booking hotel accommodations through a series of well-defined steps. Have a read at the flow chart below to understand how you should be interacting with our API endpoints when building your application. - [Endpoints overview](https://docs.liteapi.travel/reference/api-endpoints-overview.md): The provided diagram visually outlines the API endpoints available in Nuitee Connect v3, categorized into four main sections: Hotel Data API, Search API, and Booking API, Loyalty API. - [OpenAPI Specifications](https://docs.liteapi.travel/reference/openapi-specifications.md): This page collects the OpenAPI specifications for all Nuitee Connect services. Use the links below to explore endpoints, schemas, and examples for each API domain. These specs are the source of truth for integration, testing, and client generation. - [Payments & Revenue](https://docs.liteapi.travel/reference/payments.md) - [Google Hotel Center integration](https://docs.liteapi.travel/reference/google-hotel-center-integration.md) - [MCP Server for AI Agents](https://docs.liteapi.travel/reference/mcp-server.md): Nuitee Connect provides an **MCP (Model Context Protocol) server** that allows AI systems, agents, and LLM-based applications to securely access Nuitee Connect capabilities. - [Prompt for Vibe Coding tools](https://docs.liteapi.travel/reference/prompt-for-vibe-coding-tools.md): Nuitee Connect provides a ready-to-use script designed specifically for vibe coding tools like Cursor and Lovable. - [Booking Assistant AI Chatbot](https://docs.liteapi.travel/reference/liteapi-ai-chatbot.md): The Nuitee Connect AI Chatbot is a ready-to-embed chat widget that gives your users a natural language interface for finding and booking hotels. - [Retrieve rates for hotels](https://docs.liteapi.travel/reference/post_hotels-rates.md): ## Overview Search for hotel rates and availability across multiple hotels. This is your primary endpoint for finding bookable hotel rooms with real-time pricing. ## When to Use - **Display hotel listings** with prices on your search results page - **Show detailed rate options** for specific hotels users are viewing - **Support multi-room bookings** for families or groups - **Filter hotels** by location, amenities, ratings, or AI-powered semantic search ## What You Get - **Real-time rates** with availability and pricing - **Multiple room options** per hotel, sorted by price - **Complete booking details** including cancellation policies, meal plans, and room types - **Hotel information** (name, photos, address, ratings) when searching by filters ## Key Features - **Multiple search methods**: Search by hotel IDs, city/country, coordinates, Place ID, IATA code, or natural language (AI search) - **Flexible filtering**: Filter by star rating, facilities, hotel chains, accessibility, and more - **Multi-room support**: Book multiple rooms with different guest configurations in one request - **Performance optimized**: Default limit of 200 hotels (expandable to 5,000), recommended timeout of 6-12 seconds - **Price consistency**: Optional `sessionId` ensures rates stay consistent across listing and detail searches within a user session (accounts with price consistency enabled) ## Quick Start **Required fields**: `checkin`, `checkout`, `currency`, `guestNationality`, `occupancies`, plus one location method (hotel IDs, city/country, coordinates, Place ID, or IATA code) **Tip**: When searching by filters (like `aiSearch` or `cityName`), hotel data is automatically included. For direct hotel ID searches, set `includeHotelData=true` to include hotel names and photos. **Price consistency**: Generate a unique `sessionId` per user search session and include it on every rates request in that session, using the same `checkin`, and `checkout`. - [Retrieve minimum rate for hotels](https://docs.liteapi.travel/reference/post_hotels-min-rates.md): ## Overview Get the cheapest available rate for each hotel in your list. Perfect for displaying price comparisons without loading full rate details. ## When to Use - **Show price ranges** on hotel listing pages - **Quick price comparisons** across multiple hotels - **Optimize performance** when you only need the lowest price, not all rate options - **Build price filters** or sorting by price ## What You Get - **Minimum rate per hotel** - the cheapest available room option - **Basic rate information** - price, currency, and availability - **Fast response** - optimized for quick price lookups ## Key Features - **Lightweight** - Returns only the minimum rate, not all options - **Same parameters** as the main rates endpoint for consistency - **Perfect for listings** - Ideal when displaying multiple hotels where users just need to see starting prices ## Quick Start Provide a list of hotel IDs, dates, and guest occupancy. The endpoint returns the cheapest rate available for each hotel. - [1. Create a checkout session (PREBOOK)](https://docs.liteapi.travel/reference/post_rates-prebook.md): ## Overview **Step 1 of 2** in the booking flow. Create a prebook session to check the availability of a rate and get final pricing before payment. This `prebookId` needed to complete the booking. ## When to Use - **Before payment** - Always call this before completing a booking - **Rate confirmation** - Verify final pricing and availability - **Session creation** - Generate a checkout session for your payment flow ## What You Get - **Prebook ID** - Required for the next step (completing the booking) - **Final pricing** - Confirmed rates with all fees and taxes - **Terms and conditions** - Cancellation policies and booking rules - **Room details** - Complete information about the selected rooms ## Key Features - **Live availability check** - Verifies the rate is available before you collect payment - **Payment SDK support** - Set `usePaymentSdk=true` to use client-side payment forms - **Reusable** - PrebookId can be used for multiple bookings if needed ## Quick Start Provide the `offerId` from your hotel rates search and set `usePaymentSdk` (true/false). Returns a `prebookId` to use in the next step. **Next Step**: Use the `prebookId` with `/rates/book` to complete the booking. - [2. Complete a booking](https://docs.liteapi.travel/reference/post_rates-book.md): ## Overview **Step 2 of 2** in the booking flow. Complete the booking by providing guest information and payment details. This confirms the reservation and creates the final booking. ## When to Use - **After prebook** - Call this after creating a prebook session - **Payment processing** - Submit payment information to confirm booking - **Booking confirmation** - Finalize the reservation ## What You Get - **Booking ID** - Unique identifier for the confirmed booking - **Hotel confirmation code** - Reference code from the hotel - **Complete booking details** - Dates, pricing, room information - **Cancellation policies** - Terms for cancelling the booking - **Guest information** - Confirmed guest details ## Payment Methods - **ACC_CREDIT_CARD** - Direct credit card payment. In sandbox mode, this can be used to simulate a booking without getting charged. - **TRANSACTION** - Use when using Payment SDK (provide `transactionId`) - **WALLET** - Wallet payment method - **CREDIT** - Use account credit balance - **CREDIT_CARD** - Credit card payment via secure endpoint. Accepts any credit or debit card, including virtual credit cards. Send card details via `https://pci-book.liteapi.travel` using the `billingInfo` object. Contact the team to enable this on your API key. ## Testing When testing sandbox bookings, simply use the `ACC_CREDIT_CARD` payment method. This allows you to simulate a booking without getting charged. ## Required Information - **Prebook ID** - From the prebook step - **Guest details** - First name, last name, and email - **Payment information** - Payment method and details ## Quick Start Provide the `prebookId`, guest information (firstName, lastName, email), and payment details. Returns confirmed booking with booking ID and confirmation code. - [Retrieve a prebook by ID](https://docs.liteapi.travel/reference/get_prebooks-prebookid.md): ## Overview Retrieve details of an existing prebook session by its ID. Use this to fetch prebook information without creating a new session. ## When to Use - **Session recovery** - Retrieve prebook details if you've stored the prebookId - **Status checks** - Verify prebook session details before completing booking - **Payment integration** - Get prebook data needed for payment processing - **Credit balance** - Optionally include updated credit balance information ## What You Get - **Complete prebook data** - All information from the prebook session - **Rate details** - Pricing, room types, and availability - **Terms and conditions** - Cancellation policies and booking terms - **Credit balance** - Optional updated credit balance (if requested) ## Quick Start Provide the `prebookId` in the URL path. Optionally include `includeCreditBalance` query parameter to get updated credit information. - [List bookings](https://docs.liteapi.travel/reference/listbookings.md): ## Overview Search for bookings by guest ID or client reference. Perfect for displaying a guest's booking history or finding bookings by your internal reference codes. ## When to Use - **Guest booking history** - Show all bookings for a specific guest - **Reference lookup** - Find bookings by your internal reference codes - **Booking management** - List bookings for administrative purposes - **Customer support** - Quickly find bookings for support tickets ## What You Get - **Booking list** - All matching bookings with complete details - **Guest information** - Name, email, and contact details - **Stay details** - Check-in/check-out dates and hotel information - **Payment status** - Current payment and booking status - **Booking references** - Booking IDs and confirmation codes ## Search Options - **By guest ID** - Find all bookings for a specific guest - **By client reference** - Find bookings using your internal reference codes - **By customTags** - Narrow results by booking labels using `customTags=KEY:VALUE,KEY2:VALUE2` (AND across keys) - **Optional timeout** - Set request timeout (default 4 seconds) ## Quick Start Provide either `guestId` or `clientReference` (or both). Returns matching bookings with full details. - [Retrieve a booking](https://docs.liteapi.travel/reference/get_bookings-bookingid.md): ## Overview Get complete details for a specific booking by its booking ID. Returns all booking information including status, guest details, pricing, and cancellation policies. ## When to Use - **Booking details page** - Display complete booking information - **Status checks** - Verify current booking status - **Confirmation lookup** - Retrieve booking confirmation details - **Support queries** - Look up booking information for customer service ## What You Get - **Complete booking details** - All information about the booking - **Booking status** - Current status (confirmed, cancelled, etc.) - **Guest information** - Name, email, and contact details - **Stay information** - Check-in/check-out dates, hotel details - **Pricing breakdown** - Total cost, taxes, fees, and payment status - **Cancellation policies** - Terms and conditions for cancellation - **Hotel confirmation** - Hotel confirmation code and reference ## Quick Start Provide the `bookingId` in the URL path. Returns complete booking details including status and all associated information. - [Cancel a booking](https://docs.liteapi.travel/reference/put_bookings-bookingid.md): ## Overview Cancel an existing confirmed booking. Cancellation policies determine whether a full refund, partial refund, or charges apply. ## When to Use - **Guest cancellation** - Allow guests to cancel their bookings - **Administrative cancellation** - Cancel bookings from admin panels - **Policy enforcement** - Apply cancellation policies automatically ## What You Get - **Cancellation status** - Success or failure of cancellation - **Charges information** - Any fees or charges that apply - **Refund details** - Amount refunded (if applicable) - **Updated booking status** - Booking marked as cancelled ## Cancellation Outcomes - **CANCELLED** - Fully refundable, no charges - **CANCELLED_WITH_CHARGES** - Non-refundable or past cancellation deadline, charges apply - **Cancellation policies** - Applied automatically based on booking terms ## Important Notes - **Non-refundable bookings** - Will be cancelled but still charged (status: CANCELLED_WITH_CHARGES) - **Policy enforcement** - Cancellation policies are automatically applied - **Past deadline** - Cancellations after the policy deadline may incur charges ## Quick Start Provide the `bookingId` in the URL path. Returns cancellation status and any applicable charges or refunds. - [Retrieve all bookings](https://docs.liteapi.travel/reference/get_bookings.md): ## Overview Get all bookings associated with your API key, with optional filtering by date ranges. Perfect for generating reports and managing your booking inventory. ## When to Use - **Booking reports** - Generate reports of all bookings - **Date range queries** - Find bookings within specific date ranges - **Administrative overview** - View all bookings in your system - **Analytics** - Analyze booking patterns and trends ## What You Get - **Complete booking list** - All bookings linked to your API key - **Filtered results** - Optional filtering by stay dates or booking creation dates - **Booking details** - Full information for each booking - **Status information** - Current status of each booking ## Filtering Options - **Stay period** - Filter by check-in/check-out date range (`startDate`, `endDate`) - **Booking period** - Filter by when bookings were created (`bookingStartDate`, `bookingEndDate`) - **Status** - Filter by booking status (optional) ## Quick Start No parameters required for all bookings. Optionally provide date ranges to filter results. Returns all matching bookings with complete details. - [Amend guest name on a booking](https://docs.liteapi.travel/reference/put_bookings-bookingid-amend.md): ## Overview Update guest information (name and email) for an existing booking. Useful for correcting typos or updating guest details after booking. ## When to Use - **Name corrections** - Fix typos in guest names - **Email updates** - Update guest email addresses - **Guest changes** - Change guest information after booking - **Support requests** - Update booking details per customer requests ## What You Get - **Confirmation** - Success message when amendment is complete - **Updated booking** - Booking reflects the new guest information ## Editable Fields - **First name** - Guest's first name - **Last name** - Guest's last name - **Email** - Guest's email address - **Remarks** - Optional additional notes ## Limitations - **Holder only** - Only the booking holder's information can be updated - **Name and email** - Other guest details cannot be amended ## Quick Start Provide the `bookingId` and updated guest information (firstName, lastName, email). Optionally include remarks. Returns confirmation of the update. - [Amend booking checkin, checkout or occupancies](https://docs.liteapi.travel/reference/post_bookings-bookingid-alternative-prebooks.md): ## Overview **Hard Amendment** — Search for alternative rates at the same hotel and create ready-to-book prebook sessions for a confirmed booking. Used when the guest needs to change their check-in/check-out dates or room occupancy. ## When to Use - **Date changes** — Guest needs different check-in or check-out dates - **Occupancy changes** — Guest needs a different number of adults or children - **Hard amendments** — Situations where the booking must be cancelled and re-booked with new parameters ## How It Works 1. The system searches for live availability at the same hotel with the new parameters. 2. Up to `maxPrebooks` alternative rates are selected (sorted by price ascending). Defaults to 3 when omitted; capped at 10 (any larger value is silently clamped to 10). 3. A prebook session is created for each rate. 4. The caller receives a list of `prebookId` values ready to be used with `POST /rates/rebook`. ## What You Get - **Up to `maxPrebooks` prebook sessions** — Each with a `prebookId`, final pricing, cancellation policies, and room details - **Price comparison** — `priceDifferencePercent` shows how each alternative compares to the **original booking's selling price** (negative = cheaper than what the guest paid, positive = more expensive) - **Policy change flags** — `cancellationChanged` and `boardChanged` highlight any policy differences ## Completing the Amendment Pass the chosen `prebookId` and the original `bookingId` as `existingBookingId` to `POST /rates/rebook`. On success, the new booking is created **and the original booking is automatically cancelled** — no separate cancellation call is needed. ## Key Notes - The booking must be in **CONFIRMED** status. - If the original booking is non-refundable, only non-refundable alternatives are returned (unless overridden with `refundableRatesOnly`). - **Payment type is honoured** — only rates that support the original booking's payment type are returned. A pay-at-property booking only sees `PROPERTY_PAY` alternatives; every other booking (including pay-later, succeeded, credit_line) only sees `NUITEE_PAY` alternatives. Pay-later eligibility additionally requires a refundable rate, which is enforced automatically when the original booking was refundable. - The nationality and currency of the original booking are used for the availability search. - If the cancellation of the original booking fails after the new booking is created, the error is logged but the new booking is still returned. ## Quick Start 1. Call this endpoint with the `bookingId` and new `occupancies`/dates — get back up to `maxPrebooks` `prebookId` values. 2. Call `POST /rates/rebook` with the chosen `prebookId` and `existingBookingId` — new booking confirmed, original cancelled. - [Complete a hard amendment (rebook)](https://docs.liteapi.travel/reference/post_rates-rebook.md): ## Overview **Step 2 of 2** in the **hard amendment** flow. Use a `prebookId` produced by `POST /bookings/{bookingId}/alternative-prebooks` to create the replacement booking. On success, the new booking is created **and the original booking is automatically cancelled** — you do **not** need to call the cancel endpoint. ## When to Use - **After alternative-prebooks** — Once the guest has chosen one of the alternative prebooks returned by `POST /bookings/{bookingId}/alternative-prebooks`. - **Date or occupancy changes** — The guest needs different check-in/check-out dates or a different number of adults/children at the same hotel. - **Hard amendments only** — For simple guest-name updates use `PUT /bookings/{bookingId}/amend` instead. ## How It Works 1. The provided `prebookId` is validated against the booking referenced by `existingBookingId` (it must have been produced by an `alternative-prebooks` call for that booking). 2. The new booking is created with the supplier using the alternative rate. 3. The original booking is then automatically cancelled. If the cancellation fails after the new booking is confirmed, the error is logged but the new booking is still returned — contact support to reconcile. ## Payment - No payment is collected on this endpoint. The `payment.method` value is ignored — the request body must still include a `payment` object to satisfy the schema, but the server forces the method to `NONE` internally. Any price delta between the original and new rate is settled out of band. ## Refundable vs Non-refundable Originals - **Refundable original** — Returns `200 OK` with the new booking, and the original is cancelled immediately. - **Non-refundable original** — Returns `202 Accepted` with a booking amendment record. The request is queued for the Nuitee operations team to handle manually (the original booking may incur cancellation fees). ## Required Information - **prebookId** — A prebook session returned by `POST /bookings/{bookingId}/alternative-prebooks`. - **existingBookingId** — The `bookingId` of the original confirmed booking being replaced. Must match the `bookingId` that produced the prebook. - **holder** and **guests** — Same structure as `POST /rates/book`. If `holder` fields are empty they are copied from the original booking. ## Quick Start 1. Call `POST /bookings/{bookingId}/alternative-prebooks` and pick one of the returned `prebookId` values. 2. Call this endpoint with that `prebookId`, the original `bookingId` as `existingBookingId`, and guest information. 3. On success, the new booking is confirmed and the original is cancelled — no further calls are needed. - [Retrieve a list of hotels](https://docs.liteapi.travel/reference/get_data-hotels.md): ## Overview Search and retrieve hotel listings based on various criteria. Get hotel metadata including names, addresses, ratings, amenities, and images for display in your application. ## When to Use - **Hotel listings** - Display hotel search results - **Location-based search** - Find hotels by city, coordinates, or Place ID - **Hotel discovery** - Browse hotels in specific areas - **Metadata retrieval** - Get hotel information for display ## What You Get - **Hotel list** - Matching hotels with complete metadata - **Basic information** - Names, addresses, ratings, and locations - **Amenities** - Available facilities and features - **Images** - Hotel photos for display - **Identifiers** - Hotel IDs for use in rate searches ## Search Options - **By city** - Search hotels in a specific city - **By coordinates** - Find hotels near latitude/longitude with radius - **By Place ID** - Get hotels within a specific place boundary - **By hotel IDs** - Retrieve specific hotels by their IDs ## Quick Start Provide search criteria (city, coordinates+radius, placeId, or hotelIds). Returns matching hotels with complete metadata. - [Get the details of a hotel](https://docs.liteapi.travel/reference/get_data-hotel.md): ## Overview Get comprehensive details about a specific hotel including descriptions, amenities, images, location, and ratings. Perfect for displaying hotel detail pages. ## When to Use - **Hotel detail pages** - Show complete hotel information - **Booking pages** - Display hotel details before booking - **Hotel profiles** - Build rich hotel information pages - **Content display** - Show descriptions, amenities, and images ## What You Get - **Complete hotel information** - Name, address, description, and ratings - **Amenities list** - All available facilities and services - **Image gallery** - Hotel photos and images - **Location details** - Address, coordinates, and location information - **Hotel metadata** - Star rating, chain information, and classifications ## Quick Start Provide the `hotelId` as a query parameter. Returns complete hotel details including all metadata, amenities, and images. - [Get the reviews of a hotel](https://docs.liteapi.travel/reference/get_data-reviews.md): ## Overview Retrieve guest reviews and ratings for a specific hotel. Display authentic feedback from previous guests to help users make informed booking decisions. ## When to Use - **Review display** - Show guest reviews on hotel detail pages - **Rating aggregation** - Display average ratings and review counts - **Trust building** - Show authentic guest feedback - **Decision support** - Help users evaluate hotels before booking ## What You Get - **Guest reviews** - Individual review text and ratings - **Review dates** - When each review was written - **Ratings** - Numerical and textual ratings - **Guest feedback** - Detailed comments from previous guests ## Quick Start Provide the `hotelId` as a query parameter. Returns all reviews for that hotel with ratings and comments. - [Search hotel rooms by image and text (Beta)](https://docs.liteapi.travel/reference/get_data-hotels-room-search.md): ## Overview **Beta Feature** - Search hotel rooms using visual and text-based queries. Uses image search technology to match your query against room images and find hotels with rooms that match your visual preferences, amenities, or style. ## When to Use - **Visual room search** - Find rooms based on visual characteristics like "luxury modernist comfort" or "blue accessible bathroom" - **Style-based search** - Search for rooms by design style like "art deco hotel room" or "brutalist room" - **Amenity-focused search** - Find rooms with specific features like "twin room with a city view" or "room with a skylight" - **Geographic filtering** - Limit results to hotels near a specific location using coordinates or Place ID - **City and country filtering** - Filter results by city and/or country ## What You Get - **Matching hotels** - Hotels grouped by hotel ID with rooms that match your query - **Room details** - Room name, image URL, and similarity score (rounded to 3 decimals) for each matching room - **Hotel metadata** - ID, name, address, city, country, and rating for each hotel - **Geographic filtering** - Optionally limit results to a specific area using coordinates or Place ID - **City and country filters** - Filter results by city and/or country code ## Example Queries - "luxury modernist comfort" - "an extremely fun room or art deco hotel room" - "luxurious accessible bathroom or blue accessible bathroom with walk in shower" - "twin room with a city view" - "a room filled with paintings" - "a hotel room with a skylight" ## Geographic Filtering You can optionally limit search results to a specific geographic area: - **Using coordinates**: Provide `latitude`, `longitude`, and optionally `radius` (in kilometers, default: 12km) - **Using Place ID**: Provide `placeId` - the place's location will be automatically fetched and the search will use the place's viewport boundaries (or the provided `radius` if viewport is unavailable) - **Using city/country**: Provide `city` and/or `country` to filter results by location ## Quick Start Provide a `query` parameter describing the room you're looking for. Optionally add geographic filtering with `latitude`/`longitude` or `placeId` to limit results to a specific area. **Note:** This is a beta feature and may be subject to changes. - [Search hotels by semantic query (Beta)](https://docs.liteapi.travel/reference/get_data-hotels-semantic-search.md): ## Overview **Beta Feature** - Search hotels using natural language queries. Uses AI to understand search intent and find hotels that match the meaning, not just keywords. ## When to Use - **Natural language search** - Let users search with phrases like "romantic getaway in London" - **Intent-based matching** - Find hotels matching the vibe or style, not just location - **Conversational search** - Support natural language hotel discovery - **Semantic matching** - Get hotels that semantically match the query ## What You Get - **Matching hotels** - Hotels that semantically match your query - **Semantic attributes** - Tags, persona, style, location_type, and story for each hotel - **Relevance scores** - How well each hotel matches the query - **Hotel metadata** - ID, name, photos, address, city, country ## Example Queries - "Romantic getaway in London with Italian vibes" - "Hotels near Paris" - "Family-friendly beachfront hotels" ## Quick Start Provide a natural language `query` parameter. Returns hotels with semantic matching scores and attributes. **Note:** This is a beta feature and may be subject to changes. - [Ask a question about a hotel (Beta)](https://docs.liteapi.travel/reference/get_data-hotel-ask.md): ## Overview **Beta Feature** - Ask natural language questions about a specific hotel and get AI-powered answers based on the hotel's information. ## When to Use - **Hotel Q&A** - Answer customer questions about hotels - **Information lookup** - Get specific details about amenities, services, or features - **Conversational interfaces** - Build chat interfaces for hotel information - **Detailed inquiries** - Ask about specific aspects like restaurants, parking, or amenities ## What You Get - **AI-generated answers** - Relevant responses to your questions - **Hotel-specific information** - Answers based on the hotel's actual data - **Natural language responses** - Human-readable answers ## Example Questions - "What amenities does this hotel have?" - "Is there parking available?" - "What does a meal at the restaurant look like?" ## Key Features - **Web search option** - Enable `allowWebSearch` to get additional information from the web - **Hotel context** - Answers are specific to the hotel you're asking about - **Natural language** - Ask questions conversationally ## Quick Start Provide the `hotelId` and your `question`. Optionally enable `allowWebSearch` for web-enhanced answers. **Note:** This is a beta feature and may be subject to changes. - [Generate hotel highlights (Beta)](https://docs.liteapi.travel/reference/post_data-hotel-highlights.md): ## Overview **Beta Feature** - Generate short, AI-written "Smart Highlight" cards for a hotel. Each highlight is a title plus a one or two sentence description, generated directly in the requested language. **Rate Limiting**: This endpoint is rate-limited to **10 requests per minute** per API key for both sandbox and production API keys. Exceeding this limit will result in a `429 Too Many Requests` response. ## When to Use - **Hotel detail pages** - Show a few compelling reasons to consider a property - **Partner-specific tone** - Adjust voice and emphasis per surface via `tone`, `style` and per-highlight `context` ## What You Get - Exactly `count` highlights, always, in the requested order - `type` echoed back from the request so you can map each card to your own UI - `generated` indicating whether the copy is AI-generated or template fallback ## Behaviour Hotel facts (name, city, country, description) are resolved server-side from `hotelId`; the caller never supplies them. Generated copy is grounded in those facts. If AI generation fails, the endpoint still returns `200` with the requested number of neutral template highlights and `generated: false`. It never returns an empty array for a valid hotel. Results are cached, so repeated calls with an identical request body return identical copy. **Note:** This is a beta feature and may be subject to changes. - [Get the normalized tax schema of a hotel](https://docs.liteapi.travel/reference/gethoteltaxschema.md): ## Overview Returns the tax schema of a hotel as normalized static data, independent of the supply provider the rules were learned from. Each entry describes one tax or fee: whether it is already included in the room rate, whether it is a percentage of the rate or a fixed amount, and how fixed amounts scale (per adult and/or per night). ## When to Use - **Price transparency** - Show guests which taxes and fees apply at a property - **Amount-due-at-property estimates** - Excluded taxes are typically collected at the hotel - **Tax auditing** - Compare supplier-declared taxes against the reference schema ## Notes - Fixed amounts are expressed in USD - Percentage rates apply to the room rate (e.g. 13.5 means 13.5%) - The schema is learned by an offline pipeline; hotels without learned data return 404 - [Search for a list of places](https://docs.liteapi.travel/reference/get_data-places.md): ## Overview Search for places, locations, and areas using Google Places API. Returns a list of matching places that can be used to search for hotels within specific boundaries. **Pricing**: $0.01 per request ## When to Use - **Location autocomplete** - Build location search with autocomplete suggestions - **Place selection** - Let users select cities, airports, or areas - **Hotel search boundaries** - Get Place IDs to restrict hotel searches to specific regions - **Location discovery** - Find places by name or description ## What You Get - **Place list** - Multiple matching places with details - **Place IDs** - Unique identifiers for use in hotel searches - **Location information** - Names, addresses, and location types - **Formatted addresses** - Human-readable addresses for display ## Key Features - **Multiple types** - Search for cities, airports, hotels, or other place types - **Type filtering** - Specify place types (e.g., 'locality,airport,hotel') - **Smart defaults** - Automatically excludes less relevant types unless specified - **Relevance ordering** - Results sorted by relevance using Google's ranking ## Quick Start Provide a `textQuery` (e.g., "Manhattan") and optionally specify `type` to filter results. Returns matching places with Place IDs you can use in hotel searches. - [Search for a specific place](https://docs.liteapi.travel/reference/get_data-places-placeid.md): ## Overview Get detailed information about a specific place using its Place ID. Returns complete place details including boundaries and location information. **Pricing**: $0.01 per request ## When to Use - **Place details** - Get full information about a selected place - **Boundary information** - Retrieve place boundaries for hotel searches - **Location verification** - Verify place details before using in searches - **Display information** - Show place names and addresses to users ## What You Get - **Complete place details** - Full information about the place - **Boundary data** - Geographic boundaries for the place - **Location information** - Coordinates, address, and display name - **Place metadata** - Types, formatted address, and language ## Quick Start Provide the `placeId` in the URL path. Returns complete details for that specific place. - [List the cities of a country](https://docs.liteapi.travel/reference/get_data-cities.md): ## Overview Get a list of all cities within a specific country. Perfect for building location dropdowns and city selection interfaces. ## When to Use - **City dropdowns** - Populate city selection lists - **Location filters** - Filter hotels by city - **Geographic data** - Get city lists for specific countries - **Form autocomplete** - Build city autocomplete features ## What You Get - **City list** - All cities in the specified country - **City names** - Formatted city names ready for display ## Quick Start Provide the `countryCode` in ISO-2 format (e.g., "US", "GB"). Returns all cities in that country. Use the [Get Country List endpoint](/v3.0.0/reference/get_data-countries) to get country codes. - [List all countries](https://docs.liteapi.travel/reference/get_data-countries.md): ## Overview Get a complete list of all countries available in the system with their ISO-2 country codes. Essential for building country selection interfaces. ## When to Use - **Country dropdowns** - Populate country selection lists - **Location filters** - Filter hotels or searches by country - **Form inputs** - Build country selection forms - **Reference data** - Get country codes for use in other endpoints ## What You Get - **Country list** - All available countries - **ISO-2 codes** - Standard country codes (e.g., "US", "GB", "FR") - **Country names** - Full country names ## Quick Start No parameters required. Returns all countries with their ISO-2 codes. - [List all currencies](https://docs.liteapi.travel/reference/get_data-currencies.md): ## Overview Get all available currencies with their codes, names, and the countries where each currency is used. Perfect for building currency selection interfaces. ## When to Use - **Currency dropdowns** - Populate currency selection lists - **Price display** - Show prices in different currencies - **Currency conversion** - Get currency information for conversion - **Reference data** - Get currency codes for use in booking endpoints ## What You Get - **Currency list** - All available currencies - **Currency codes** - ISO currency codes (e.g., "USD", "EUR", "GBP") - **Currency names** - Full currency names - **Country mapping** - Countries where each currency is used ## Quick Start No parameters required. Returns all currencies with codes, names, and country mappings. - [List the IATA codes](https://docs.liteapi.travel/reference/get_data-iatacodes.md): ## Overview Get IATA (International Air Transport Association) airport codes with airport names, coordinates, and country information. Useful for airport-based hotel searches. ## When to Use - **Airport searches** - Find hotels near airports - **Location selection** - Let users search by airport codes - **Geographic data** - Get airport locations and coordinates - **Reference data** - Get IATA codes for use in hotel searches ## What You Get - **Airport list** - All available airports with IATA codes - **Airport names** - Full airport names - **Coordinates** - Latitude and longitude for each airport - **Country codes** - ISO-2 country codes for each airport ## Quick Start No parameters required. Returns all airports with IATA codes, names, coordinates, and country information. - [List Hotel Facilities with Multi-Language Support](https://docs.liteapi.travel/reference/get_data-facilities.md): ## Overview Get all available hotel facilities (amenities) with multi-language translations. Use these facility IDs to filter hotel searches by amenities. ## When to Use - **Facility filters** - Build amenity filtering in hotel searches - **Facility display** - Show available facilities with translated names - **Multi-language support** - Display facilities in user's language - **Reference data** - Get facility IDs for use in search filters ## What You Get - **Facility list** - All available hotel facilities - **Facility IDs** - Numeric IDs for use in search filters - **Multi-language names** - Facility names in multiple languages - **Translations** - Localized facility names ## Quick Start No parameters required. Returns all facilities with IDs and multi-language translations. Use facility IDs in hotel search filters. - [List of hotel types](https://docs.liteapi.travel/reference/get_data-hoteltypes.md): ## Overview Get all available hotel type classifications (e.g., resort, boutique, business hotel). Use type IDs to filter hotel searches. ## When to Use - **Type filters** - Filter hotels by type in search - **Type display** - Show hotel type classifications - **Reference data** - Get hotel type IDs for filtering ## What You Get - **Hotel type list** - All available hotel types - **Type IDs** - Numeric IDs for use in search filters - **Type names** - Hotel type classifications ## Quick Start No parameters required. Returns all hotel types with IDs. Use type IDs in hotel search filters. - [List of hotel chains](https://docs.liteapi.travel/reference/get_data-chains.md): ## Overview Get all available hotel chains (e.g., Marriott, Hilton, IHG). Use chain IDs to filter hotel searches by brand. ## When to Use - **Chain filters** - Filter hotels by chain/brand - **Brand selection** - Let users search for specific hotel chains - **Reference data** - Get chain IDs for use in search filters ## What You Get - **Chain list** - All available hotel chains - **Chain IDs** - Numeric IDs for use in search filters - **Chain names** - Hotel chain/brand names ## Quick Start No parameters required. Returns all hotel chains with IDs. Use chain IDs in hotel search filters. - [List of supported languages](https://docs.liteapi.travel/reference/get_data-languages.md): ## Overview Get all supported languages for hotel translations and content localization. Use language codes to request hotel data in specific languages. ## When to Use - **Language selection** - Display available languages to users - **Content localization** - Get language codes for API requests - **Multi-language support** - Build language switchers in your application - **Reference data** - Validate language codes before making requests ## What You Get - **Language list** - All supported and enabled languages - **Language codes** - ISO 639-1 codes (e.g., 'en', 'es', 'fr') - **Language names** - Human-readable language names in English ## Quick Start No parameters required. Returns all supported languages with codes and names. Use language codes in hotel search and detail requests. - [Create a new voucher](https://docs.liteapi.travel/reference/post_vouchers.md): ## Overview Create discount vouchers that customers can apply to their hotel and flight bookings. Supports percentage discounts, fixed amounts, and points redemption vouchers. ## When to Use - **Promotional campaigns** - Create discount codes for marketing - **Customer rewards** - Generate vouchers for loyal customers - **Special offers** - Create time-limited discount vouchers - **Points redemption** - Generate vouchers from loyalty points ## What You Get - **Voucher object** - Complete voucher details including code and settings - **Usage tracking** - Remaining uses count - **Validation** - Confirmation that the voucher was created successfully ## Key Features - **Multiple discount types** - Percentage, fixed amount, or points redemption - **Flexible rules** - Set minimum spend, maximum discount, and usage limits - **Validity control** - Define start and end dates - **Guest assignment** - Optionally assign to specific guests - **Applies to hotels and flights** - Pass the `voucherCode` in the `voucherCode` field of `/rates/prebook` (hotels) or `/flights/prebooks` (flights) to redeem the discount at checkout ## Quick Start Provide voucher code, discount type, value, currency, validity dates, usage limits, and status. Returns the created voucher with all details. - [Retrieve all vouchers](https://docs.liteapi.travel/reference/get_vouchers.md): ## Overview Get a paginated list of all vouchers in your system, including active and inactive vouchers with their current status. ## When to Use - **Voucher management** - View all vouchers in your admin panel - **Inventory overview** - See all available discount codes - **Status monitoring** - Check which vouchers are active - **Reporting** - Generate lists of all vouchers for analysis ## What You Get - **Complete voucher list** - All vouchers with full details - **Discount information** - Type, value, and currency for each voucher - **Validity status** - Start/end dates and current status - **Usage tracking** - Remaining uses for each voucher ## Pagination Results are paginated. Use the `page` and `limit` query parameters to navigate through the list, e.g. `/vouchers?page=5&limit=10`. ## Quick Start Optionally provide `page` and `limit` query parameters. Returns a paginated list of vouchers with complete details including codes, discounts, validity, and usage counts. - [Retrieve a specific voucher](https://docs.liteapi.travel/reference/get_vouchers-voucherid.md): ## Overview Get complete details for a specific voucher by its ID, including discount rules, validity, and usage information. ## When to Use - **Voucher lookup** - Find details for a specific voucher code - **Validation** - Verify voucher details before applying to bookings - **Details display** - Show voucher information to customers - **Support** - Look up voucher information during customer service ## What You Get - **Complete voucher details** - All information about the voucher - **Discount rules** - Type, value, minimum spend, maximum discount - **Validity information** - Start/end dates and current status - **Usage data** - Current usage count and remaining uses ## Quick Start Provide the voucher ID in the URL path. Returns complete voucher information. - [Update a voucher](https://docs.liteapi.travel/reference/put_vouchers-id.md): ## Overview Modify an existing voucher's settings, including discount values, validity periods, usage limits, and status. ## When to Use - **Extend validity** - Update voucher end dates - **Adjust discounts** - Change discount values or types - **Update limits** - Modify usage limits or minimum spend - **Status changes** - Activate or deactivate vouchers ## What You Get - **Confirmation** - Success message when voucher is updated - **Updated voucher** - Voucher reflects the new settings ## Important Notes - **Read-only if used** - Vouchers that have been used in bookings cannot be modified (returns 404) - **All fields required** - Must provide all required fields, not just the ones you want to change ## Quick Start Provide the voucher ID and updated fields. Returns confirmation of the update. - [Update voucher status](https://docs.liteapi.travel/reference/put_vouchers-id-status.md): ## Overview Quickly activate or deactivate a voucher without updating other fields. Perfect for temporarily disabling vouchers. ## When to Use - **Temporary disable** - Deactivate vouchers without deleting them - **Reactivate vouchers** - Turn inactive vouchers back on - **Status management** - Quickly toggle voucher availability ## What You Get - **Confirmation** - Success message confirming status change - **Updated status** - Voucher status changed to active or inactive ## Quick Start Provide the voucher ID and the new `status` ("active" or "inactive"). Returns confirmation of the status update. - [Retrieve voucher usage history](https://docs.liteapi.travel/reference/get_vouchers-history.md): ## Overview Get a complete history of all voucher redemptions across your system, showing which vouchers were used, when, and for which bookings. ## When to Use - **Usage analytics** - Track voucher redemption patterns - **Performance reporting** - See which vouchers are most popular - **Audit trail** - Maintain records of voucher usage - **Marketing insights** - Understand voucher effectiveness ## What You Get - **Usage records** - Each voucher redemption with full details - **Booking information** - Booking IDs and hotel or flight names where vouchers were used - **Guest details** - Email addresses of guests who used vouchers - **Discount amounts** - Total discount applied per usage - **Timestamps** - When each voucher was redeemed ## Quick Start No parameters required. Returns complete usage history for all vouchers across hotel and flight bookings, including booking details and discount amounts. - [Delete a voucher](https://docs.liteapi.travel/reference/delete-voucher.md): ## Overview Permanently remove a voucher from your system. Use with caution - deleted vouchers cannot be recovered. ## When to Use - **Cleanup** - Remove expired or unused vouchers - **Error correction** - Delete vouchers created by mistake - **Inventory management** - Remove vouchers no longer needed ## What You Get - **Confirmation** - Success message when voucher is deleted ## Important Notes - **Permanent action** - Deleted vouchers cannot be restored - **Usage check** - Ensure vouchers aren't needed before deleting ## Quick Start Provide the voucher ID in the URL path. Returns confirmation of deletion. - [Get aggregated price index for a city](https://docs.liteapi.travel/reference/getpriceindexcity.md): ## Overview Retrieve aggregated historical price index data for all hotels in a specific city. Returns average per-night prices aggregated by calendar day across all hotels in the city, providing city-level pricing trends. **⚠️ Beta Feature**: This endpoint is currently in beta. The API structure and behavior may change in future versions. **Pricing**: $0.05 per request **Rate Limiting**: This endpoint is rate-limited to **10 requests per minute** for both sandbox and production API keys. Exceeding this limit will result in a `429 Too Many Requests` response. ## When to Use - **City-level price analysis** - Analyze average pricing trends for an entire city - **Market research** - Compare pricing across different cities - **Destination pricing** - Get aggregated pricing data for a destination - **City pricing dashboards** - Build visualizations of city-level price trends ## What You Get - **City-level aggregation** - Average prices aggregated across all hotels in the city (up to 1,000 hotels) - **Per-night prices** - Average price per night for each calendar day - **Daily aggregation** - One entry per day with aggregated pricing data - **Future dates only** - Only returns data for future check-in dates (defaults to today onwards) ## Key Features - **Automatic hotel discovery** - Automatically finds hotels in the specified city (up to 1,000) - **City-level aggregation** - Prices are averaged across all hotels in the city, not per hotel - **Per-night pricing** - Prices are normalized to per-night rates - **Future-focused** - Only queries check-in dates in the future by default - **Flexible date ranges** - Optional date filtering with sensible defaults ## Parameters - `countryCode` (required): ISO-2 country code (e.g., 'US', 'GB', 'FR') - `cityName` (required): City name (case-insensitive) - `fromDate` (optional): Start date in YYYY-MM-DD format. Defaults to today. - `toDate` (optional): End date in YYYY-MM-DD format. Defaults to 1 year from today. - [Get price index for hotels](https://docs.liteapi.travel/reference/getpriceindexhotels.md): ## Overview Retrieve historical price index data for a list of hotels. Returns average per-night prices aggregated by calendar day, allowing you to analyze pricing trends and patterns. **⚠️ Beta Feature**: This endpoint is currently in beta. The API structure and behavior may change in future versions. **Pricing**: $0.05 per request **Rate Limiting**: This endpoint is rate-limited to **10 requests per minute** for both sandbox and production API keys. Exceeding this limit will result in a `429 Too Many Requests` response. ## When to Use - **Price trend analysis** - Analyze how hotel prices change over time - **Price forecasting** - Use historical data to predict future pricing - **Market research** - Compare pricing across multiple hotels - **Pricing dashboards** - Build visualizations of hotel price trends ## What You Get - **Per-night prices** - Average price per night for each calendar day - **Daily aggregation** - One entry per day with aggregated pricing data - **Multiple hotels** - Query up to 50 hotels in a single request - **Future dates only** - Only returns data for future check-in dates (defaults to today onwards) ## Key Features - **Per-night pricing** - Prices are normalized to per-night rates regardless of stay duration - **Daily aggregation** - Each day has a single entry with the average per-night price across all stays that include that day - **Future-focused** - Only queries check-in dates in the future by default - **Flexible date ranges** - Optional date filtering with sensible defaults - **Hotel limit** - Maximum 50 hotel IDs per request ## Parameters - `hotelIds` (required): Comma-separated list of hotel IDs. Maximum 50 hotel IDs allowed. - `fromDate` (optional): Start date in YYYY-MM-DD format. Defaults to today. - `toDate` (optional): End date in YYYY-MM-DD format. Defaults to 1 year from today. - [Get cached public price for a hotel](https://docs.liteapi.travel/reference/getpublicprice.md): ## Overview Retrieve cached public price data for a specific hotel and occupancy. This endpoint returns pricing information sourced from public booking platforms (e.g., Booking.com, Expedia) that has been pre-fetched and cached. It applies occupancy canonicalization automatically, so callers don't need to replicate that logic. **⚠️ Beta Feature**: This endpoint is currently in beta. The API structure and behavior may change in future versions. **Rate Limiting**: This endpoint is rate-limited to **10 requests per minute** for both sandbox and production API keys. Exceeding this limit will result in a `429 Too Many Requests` response. ## When to Use - **Price comparison** - Compare your negotiated rates against publicly available prices - **Rate validation** - Verify that your offered rates are competitive before displaying to end users - **Market intelligence** - Understand public pricing trends for specific hotels and dates ## What You Get - **amount** - The best (lowest) cached public price for the stay in the specified currency - **nightlyAmount** - The best (lowest) nightly public price - **currency** - Currency code (USD) - **provider** - Normalized provider identifier for the best offer (e.g., `cheaptickets`) - **rawObservedText** - Raw observed price text from the source - **offers** - Public price offers from multiple booking providers - **fetchedAt** - When the price was last retrieved from the source - **expiresAt** - When this cached price expires and should no longer be used ## Key Features - **Occupancy-specific** - Prices are stored per occupancy configuration; query params must match write-time occupancy - **Negative cache aware** - Returns 404 for both cache misses and negative cache entries (hotels with no public price found) - **Low latency** - Direct cache lookup, no upstream API calls ## Parameters - `hotelId` (required): The liteAPI hotel ID (e.g., `lpec902`) - `checkin` (required): Check-in date in YYYY-MM-DD format - `checkout` (required): Check-out date in YYYY-MM-DD format - `adults` (required): Number of adult guests - `childrenAges` (optional): Comma-separated ages of children (e.g., `5,8`) - `currency` (optional): Currency code; if present, must be `USD` - [Retrieve weekly analytics](https://docs.liteapi.travel/reference/post_analytics-weekly.md): ## Overview Get weekly aggregated sales and booking data broken down by week. Perfect for tracking week-over-week performance trends. ## When to Use - **Weekly performance dashboards** - Show sales trends by week - **Week-over-week comparisons** - Identify growth patterns - **Business reporting** - Generate weekly reports for stakeholders - **Performance monitoring** - Track weekly sales metrics ## What You Get - **Weekly sales totals** - Aggregated sales revenue per week - **Week labels** - Human-readable week identifiers (e.g., "week 12") - **Time-series data** - Ordered by week for easy charting ## Quick Start Provide a date range (`from` and `to` dates). The endpoint returns sales data grouped by week within that range. - [Retrieve detailed analytics report](https://docs.liteapi.travel/reference/post_analytics-report.md): ## Overview Get comprehensive analytics covering sales, bookings, commissions, and revenue for your date range. This is your complete business intelligence endpoint. ## When to Use - **Executive dashboards** - Complete business overview - **Financial reporting** - Track revenue, sales, and commissions - **Booking analysis** - Monitor confirmed vs cancelled bookings - **Performance tracking** - Daily breakdowns of key metrics ## What You Get - **Sales revenue** - Daily sales totals with currency - **Booking counts** - Confirmed and cancelled bookings per day - **Commission data** - Commission earned per day - **Revenue breakdown** - Total revenue calculations - **Aggregated totals** - Summary statistics for the entire period ## Key Features - **Daily granularity** - See day-by-day performance - **Multiple currencies** - Currency information included - **Complete metrics** - Sales, bookings, commissions, and revenue in one response - **Time-series ready** - Data formatted for easy charting ## Quick Start Provide start and end dates. Returns detailed daily analytics plus aggregated totals for the period. - [Retrieve market analytics](https://docs.liteapi.travel/reference/post_analytics-markets.md): ## Overview Analyze your bookings and sales by customer nationality/market. Understand which countries drive the most business. ## When to Use - **Market analysis** - Identify top-performing markets - **Geographic insights** - Understand customer distribution - **Marketing optimization** - Focus efforts on high-value markets - **Business intelligence** - Track performance by nationality ## What You Get - **Sales by nationality** - Total sales per customer country - **Booking counts** - Number of bookings per market - **Currency information** - Sales currency for each market - **Ranked results** - Markets sorted by performance ## Quick Start Provide a date range. Returns sales and booking data grouped by customer nationality (ISO country code). - [Most booked hotels](https://docs.liteapi.travel/reference/post_analytics-hotels.md): ## Overview Get a ranked list of your top-performing hotels by booking volume and sales. Perfect for identifying your best-selling properties. ## When to Use - **Hotel performance dashboards** - Show top hotels by bookings - **Sales analysis** - Identify highest-revenue properties - **Inventory insights** - Understand which hotels drive business - **Partnership optimization** - Focus on high-performing hotel relationships ## What You Get - **Hotel rankings** - Hotels sorted by total bookings - **Booking counts** - Total bookings per hotel - **Sales totals** - Revenue generated per hotel - **Location data** - City and country for each hotel - **Hotel identifiers** - Hotel ID and name for reference ## Quick Start Provide a date range. Returns hotels ranked by total bookings, including booking counts, sales, and location information. - [Commission earnings report](https://docs.liteapi.travel/reference/post_commissions-report.md): ## Overview Returns commission earnings on the account for the given date range. Each day in the range includes the total commission amount and the average commission percentage. ## When to Use - **Commission tracking** - Monitor daily commission earnings - **Revenue analysis** - Understand commission as a percentage of sales - **Financial reporting** - Report commission totals and averages by day - **Performance dashboards** - Chart commission trends over time ## What You Get - **Daily amounts** - Total commission earned per day - **Daily percentage** - Average commission percentage per day - **Time-series data** - One entry per day, ordered by date ## Quick Start Provide a date range (`from` and `to`) and optionally `sandbox` to filter by environment. Returns an array of daily commission amounts and percentages. - [Guest nationality (source market) report](https://docs.liteapi.travel/reference/get_bookings-guest-nationality-report.md): ## Overview Returns analytics on the source markets (guest nationality) of bookings. Compares the current period to the previous period of equal length, with per-nationality booking counts, sales in USD, average booking value, and period-over-period change. ## When to Use - **Source market analysis** - See which nationalities drive the most bookings and sales - **Period comparison** - Compare current vs previous period totals and per-nationality growth - **Geographic dashboards** - Track performance by guest country (ISO code) - **Marketing and sales planning** - Identify growing or declining markets ## What You Get - **Period definition** - Date ranges for current and previous periods - **Summary** - Total sales (USD), change percent/amount, and count of nationalities - **Per-nationality data** - For each guest nationality: booking count, total sales USD, avg booking value; current and previous period; and change (sales percent/amount, booking count change) - **New markets** - Nationalities with no previous-period data have `previous_period: null` and change expressed as 100% growth ## Quick Start Pass query parameters `from`, `to`, and `sandbox`. The API derives the previous period (same length, immediately before). Returns period metadata, summary totals, and an array of nationality-level metrics. - [Destinations report (by destination country)](https://docs.liteapi.travel/reference/get_bookings-source-markets-report.md): ## Overview Returns analytics on **destinations** (the country where the hotel is located). Compares the current period to the previous period of equal length, with per-destination booking count, hotel count, sales in USD, average booking value, and period-over-period change. ## When to Use - **Destination performance** - See which countries (hotel locations) drive the most bookings and sales - **Period comparison** - Compare current vs previous period totals and per-destination growth - **Geographic dashboards** - Track performance by destination country (ISO code) - **Inventory and commercial planning** - Identify growing or declining destinations ## What You Get - **Period definition** - Date ranges for current and previous periods - **Summary** - Total sales (USD), change percent/amount, and count of destination countries - **Per-destination data** - For each country: booking count, hotel count, total sales USD, avg booking value; current and previous period; and change (sales percent/amount, booking count change) - **New or inactive destinations** - Countries with no previous-period data have `previous_period: null`; destinations with no current-period activity may have zeros and negative change ## Quick Start Pass query parameters `from`, `to`, and `sandbox`. The API derives the previous period (same length, immediately before). Returns period metadata, summary totals, and an array of destination-level metrics. - [Properties (hotels) sales report](https://docs.liteapi.travel/reference/get_bookings-hotels-sales-report.md): ## Overview Returns analytics on **properties** (hotels): per-hotel sales, buying price, profit, and profit margin. Compares the current period to the previous period of equal length. Results are ordered by current-period sales (highest first) and limited by the `limit` parameter. ## When to Use - **Property performance** - See which hotels drive the most sales and profit - **Period comparison** - Compare current vs previous period sales, profit, and bookings per hotel - **Profit analysis** - Track total_buying_price_usd, total_profit_usd, and profit_margin_percent by property - **Top properties dashboards** - Rank hotels by sales or profit ## What You Get - **Period definition** - Date ranges for current and previous periods - **Summary** - Totals for sales (USD), profit (USD), bookings, count of hotels in the result, and average profit margin percent; all with period-over-period change - **Per-hotel data** - For each property: hotel_id, hotel_name, city, country; current and previous period (booking_count, total_sales_usd, avg_booking_value_usd, total_buying_price_usd, total_profit_usd, profit_margin_percent); and change (sales/profit percent and amount, booking_count_change) - **New properties** - Hotels with no previous-period data have `previous_period: null` ## Quick Start Pass query parameters `from`, `to`, `sandbox`, and optionally `limit` (default controls how many top hotels are returned). The API derives the previous period (same length, immediately before). Returns period metadata, summary totals, and an array of hotel-level metrics. - [Search bookings by text](https://docs.liteapi.travel/reference/searchbookings.md): ## Overview Search for bookings by free-text query. Matches guest names, booking IDs, hotel names, and other booking-related fields. Results are paginated. ## When to Use - **Admin or support lookup** - Find bookings by guest name, hotel name, or partial ID - **Text search** - Search across multiple fields with a single query string - **Paginated results** - Control page size and page index via request body ## What You Get - **Matching bookings** - List of bookings matching the query with key fields - **Pagination** - `page`, `rowsPerPage`, and the search `query` echoed back - **Credit line billing** - When applicable, billing info (credit line ID, billed amount USD, billed at date, payment ID) ## Request Body - **query** (required) - Text to search for (e.g. guest name, hotel name, booking ID) - **page** - Zero-based page index (default 0) - **rowsPerPage** - Number of results per page (e.g. 5) - **sand_box** - Filter by environment (e.g. "false" for production) ## Quick Start POST a JSON body with `query`, `page`, and `rowsPerPage`. Response includes `data` array, `success`, and pagination fields. - [Fetch all guests](https://docs.liteapi.travel/reference/get_guests.md): ## Overview Retrieve a complete list of all guests enrolled in your loyalty program with their points balance and booking history. ## When to Use - **Guest management** - View all loyalty program members - **Points administration** - Check points balances across all guests - **Customer support** - Look up guest information quickly - **Reporting** - Generate lists of loyalty program participants ## What You Get - **Guest profiles** - Name, email, phone number for each guest - **Points balance** - Current points and upcoming points (pending from bookings) - **Booking history** - List of booking IDs associated with each guest - **Account metadata** - Creation and update timestamps ## Quick Start No parameters required. Returns all guests with their loyalty program details. - [Fetch a specific guest](https://docs.liteapi.travel/reference/get_guests-guestid.md): ## Overview Get detailed information about a specific guest by their ID, including loyalty points and booking history. ## When to Use - **Customer profiles** - Display guest information on their account page - **Points lookup** - Check a specific guest's points balance - **Booking history** - Show a guest's past bookings - **Support tickets** - Quickly access guest details during support ## What You Get - **Complete guest profile** - Personal information (name, email, phone) - **Points summary** - Current available points and upcoming points - **Booking list** - All booking IDs associated with this guest - **Account status** - Account creation and update information ## Quick Start Provide the guest ID in the URL path. Returns complete guest information including points and bookings. - [Fetch a guest's bookings](https://docs.liteapi.travel/reference/get_guests-guestid-bookings.md): ## Overview Get all loyalty transactions for a specific guest, showing points earned and cashback rates used for each booking. ## When to Use - **Points history** - Show guests their points earning history - **Transaction details** - Display detailed booking transactions - **Cashback tracking** - Show cashback rates applied to bookings - **Account statements** - Generate points activity reports ## What You Get - **Transaction list** - All loyalty transactions for the guest - **Points per booking** - Points earned (or deducted) for each booking - **Cashback rates** - Cashback percentage used for each transaction - **Booking references** - Booking IDs linked to each transaction - **Timestamps** - When each transaction occurred ## Quick Start Provide the guest ID in the URL path. Returns all loyalty transactions with points and cashback details. - [Fetch a guest's vouchers](https://docs.liteapi.travel/reference/get_guests-guestid-vouchers.md): ## Overview Retrieve all vouchers available to a specific guest, including discount codes, validity periods, and usage limits. ## When to Use - **Voucher display** - Show available vouchers on a guest's account page - **Discount management** - Check which vouchers a guest can use - **Validity checking** - Verify if vouchers are still active - **Usage tracking** - Monitor voucher usage counts ## What You Get - **Voucher list** - All vouchers assigned to the guest - **Discount details** - Type (percentage/fixed), value, and currency - **Validity period** - Start and end dates for each voucher - **Usage information** - Current usage count and usage limits - **Status** - Active/inactive status of each voucher ## Quick Start Provide the guest ID in the URL path. Returns all vouchers available to that guest. - [Update the loyalty program](https://docs.liteapi.travel/reference/put_loyalties.md): ## Overview Configure your loyalty program settings, including enabling/disabling the program and setting cashback rates. ## When to Use - **Program activation** - Enable or disable your loyalty program - **Rate adjustments** - Update cashback percentages - **Program management** - Change loyalty program configuration - **A/B testing** - Test different cashback rates ## What You Get - **Confirmation** - Updated program settings - **Status** - Current program status (enabled/disabled) - **Cashback rate** - Active cashback percentage ## Key Features - **Enable/disable** - Turn your loyalty program on or off - **Cashback control** - Set the percentage guests earn (e.g., 0.1 = 10%) - **Immediate effect** - Changes apply to new bookings right away ## Quick Start Send the new `status` ("enabled" or "disabled") and `cashbackRate` (decimal, e.g., 0.1 for 10%). Both fields are required. - [Get the loyalty program settings](https://docs.liteapi.travel/reference/get_loyalties.md): ## Overview Retrieve your current loyalty program configuration, including whether it's active and what cashback rate is set. ## When to Use - **Settings display** - Show current program configuration in admin panels - **Status checks** - Verify if the loyalty program is enabled - **Rate verification** - Check current cashback rates - **Configuration review** - Review program settings before making changes ## What You Get - **Program status** - Whether the program is enabled or disabled - **Cashback rate** - Current percentage guests earn - **Currency** - Cashback currency setting ## Quick Start No parameters required. Returns current loyalty program settings. - [Fetch a guest's loyalty points](https://docs.liteapi.travel/reference/get_guests-guestid-loyalty-points.md): ## Overview Get a guest's current available points and upcoming points (points pending from confirmed bookings). ## When to Use - **Points display** - Show points balance on guest account pages - **Points checking** - Quick lookup of available points - **Pending points** - Display points that will be awarded after stays - **Balance verification** - Verify points before redemption ## What You Get - **Current points** - Points available for immediate redemption - **Upcoming points** - Points that will be awarded from confirmed bookings ## Quick Start Provide the guest ID in the URL path. Returns both current and upcoming points balances. - [Redeem a guest's loyalty points](https://docs.liteapi.travel/reference/post_guests-guestid-loyalty-points-redeem.md): ## Overview Convert a guest's loyalty points into a discount voucher. Points are converted at a rate of **10 points = $1 USD** (or equivalent in the specified currency). ## When to Use - **Points redemption** - Allow guests to convert points to vouchers - **Reward fulfillment** - Create discount vouchers from points - **Loyalty rewards** - Enable points-to-cash conversion ## What You Get - **Voucher code** - Unique code the guest can use for discounts - **Voucher details** - Discount type, value, validity period, and usage limits - **Fixed amount voucher** - Voucher with a specific discount value - **Shareable voucher** - Can be used by other guests ## Key Features - **Conversion rate** - 10 points = $1 USD (or equivalent) - **Currency support** - Specify the currency for the voucher value - **Shareable** - Vouchers can be shared with other guests - **Fixed amount** - Creates a fixed discount amount voucher ## Quick Start Provide the guest ID and specify `points` (amount to redeem) and `currency` (e.g., "USD"). Returns a voucher code and details. - [Retrieve supply customization settings](https://docs.liteapi.travel/reference/get_supply-customization.md): ## Overview Get your current supply customization preferences, including advanced accessibility options for hotel searches. ## When to Use - **Settings display** - Show current customization settings in admin panels - **Configuration checks** - Verify your current preferences - **Feature verification** - Check if advanced accessibility is enabled ## What You Get - **Current settings** - Your active supply customization configuration - **Advanced accessibility flag** - Whether advanced accessibility options are enabled ## Quick Start No parameters required. Returns your current supply customization settings. - [Update supply customization settings](https://docs.liteapi.travel/reference/put_supply-customization.md): ## Overview Configure your supply customization preferences, including enabling or disabling advanced accessibility options for hotel searches. ## When to Use - **Enable features** - Turn on advanced accessibility filtering - **Customize supply** - Adjust how hotel results are filtered - **Accessibility control** - Control whether advanced accessibility hotels are included ## What You Get - **Updated settings** - Confirmation with your new configuration - **Current state** - Your active supply customization settings ## Key Features - **Advanced accessibility** - Enable/disable filtering for hotels with advanced accessibility features - **Search impact** - Settings affect hotel search results ## Quick Start Provide `advancedAccessibility` (boolean) to enable or disable advanced accessibility options. Returns updated settings. - [Get airline by IATA code](https://docs.liteapi.travel/reference/get_data-flights-airlines-iatas-iatacode.md): ## Overview Retrieve full details for a specific airline using its 2-letter IATA code. ## When to Use - **Airline display** - Show airline name, logo, and alliance for a given IATA code - **Flight result enrichment** - Fetch airline details to display alongside search results - **Data validation** - Verify an airline code and retrieve its metadata ## What You Get - **Airline details** including name, IATA/ICAO codes, and country - **Alliance membership** (Star Alliance, oneworld, SkyTeam, or Vanilla Alliance) - **Logo URL** for displaying the airline's logo in your UI - **Active status** indicating whether the airline is currently operating ## Quick Start Provide the 2-letter IATA code (e.g., `AA` for American Airlines) in the URL path. - [List airlines](https://docs.liteapi.travel/reference/get_data-flights-airlines.md): ## Overview Retrieve a list of airlines with optional filtering by name, alliance, and active status. ## When to Use - **Airline directory** - Build a searchable list of airlines for display or filtering - **Alliance filtering** - Filter airlines by alliance membership (Star Alliance, oneworld, SkyTeam) - **Active airlines** - Retrieve only currently operating airlines ## What You Get - **Full airline records** including name, IATA/ICAO codes, country, alliance, and logo URL - **Alliance membership** for each airline - **Active status** to identify currently operating carriers - **Filtered results** based on query, alliance, and active status parameters ## Quick Start Call with no parameters to get all airlines. Use `q` to search by name, `alliance` to filter by alliance, and `activeOnly=true` to exclude inactive carriers. - [List airline IATA codes](https://docs.liteapi.travel/reference/get_data-flights-airlines-iatas.md): ## Overview Retrieve a lightweight list of airline IATA codes with names for autocomplete and lookup purposes. ## When to Use - **Autocomplete dropdowns** - Populate airline search inputs with a minimal list - **Client-side filtering** - Download the full list once and filter locally - **Code validation** - Build a lookup table of valid airline codes ## What You Get - **IATA codes** for all airlines in the database - **Airline names** paired with each code - **Active filtering** available via the `activeOnly` parameter ## Quick Start Call with no parameters to get all airline IATA codes and names. Use `activeOnly=true` to filter out inactive airlines. - [Get airport by IATA code](https://docs.liteapi.travel/reference/get_data-flights-airports-iatas-iatacode.md): ## Overview Retrieve detailed information for a specific airport using its 3-letter IATA code. ## When to Use - **Airport display** - Show airport name, city, and country for a given IATA code - **Flight result enrichment** - Fetch airport details to display alongside origin/destination in search results - **Autocomplete validation** - Verify an airport code and retrieve its full details ## What You Get - **Airport details** including name, city, country, and timezone - **IATA and ICAO codes** for the airport - **Geographic coordinates** (latitude and longitude) - **Country and city** information for display purposes ## Quick Start Provide the 3-letter IATA code (e.g., `JFK` for John F. Kennedy International) in the URL path. - [List airport IATA codes](https://docs.liteapi.travel/reference/get_data-flights-airports-iatas.md): ## Overview Retrieve a lightweight list of airport IATA codes with names for autocomplete and lookup purposes. ## When to Use - **Autocomplete dropdowns** - Populate airport search inputs with a full list of codes and names - **Client-side filtering** - Download the full list once and filter locally - **Code validation** - Build a lookup table of valid airport codes ## What You Get - **IATA codes** for all airports in the database - **Airport names** paired with each code - **Filtered results** when the `q` query parameter is provided ## Quick Start Call with no parameters to get all airport codes and names. Use the `q` parameter to filter by name or code. - [Search airports](https://docs.liteapi.travel/reference/get_data-flights-airports.md): ## Overview Search for airports by name, city, or IATA code using a text query. Returns matching airports for use in autocomplete and search inputs. ## When to Use - **Airport autocomplete** - Power origin/destination search inputs with type-ahead suggestions - **Airport discovery** - Find airports in a city or region by name - **Search validation** - Look up airports before constructing a flight search request ## What You Get - **Matching airports** ranked by relevance to the query - **IATA codes** for `legs[].origin` and `legs[].destination` on `POST /flights/rates` - **City and country** details for display purposes - **Geographic coordinates** for map-based interfaces ## Quick Start Provide a `q` query string (minimum 2 characters) to search by airport name, city, or code. Returns matching airports ordered by relevance. - [Search for flights (legs-based itinerary)](https://docs.liteapi.travel/reference/post_flights-rates.md): ## Overview Search for available flights with real-time pricing from multiple providers. The itinerary **must** be sent as a non-empty `legs` array. Each leg follows the provider **SearchLeg** shape: required `origin`, `destination`, and `date` (YYYY-MM-DD); optional `direction` (`OUTBOUND` or `INBOUND`); optional per-leg `filters` that override global `filters` for that leg only. **Not supported:** top-level `origin`, `destination`, `departureDate`, or `returnDate` — use `legs` only. ## When to Use - **Listings** — live prices for search results UI - **One-way, round-trip, or multi-city** — one leg per segment, in order - **Filtering** — cabin class, stops, price, refundability, times (globally or per leg) - **Streaming** — incremental provider results over SSE ## What You Get - Offers from multiple providers - Itineraries with segments, layovers, and durations - Price breakdown (fares, taxes, fees) and baggage hints ## Key Features - Multi-provider aggregation in one request - **SSE:** send header `Accept: text/event-stream` on `POST /flights/rates`, or `POST /flights/rates/stream` with the same JSON body - Global `filters`, `sort` ## Quick Start **Required:** `legs` (at least one object with `origin`, `destination`, `date`), `adults` (≥ 1), `currency` **Round-trip:** two legs (e.g. outbound then return with `direction` `OUTBOUND` / `INBOUND`). **One-way:** one leg. - [Verify flight offer](https://docs.liteapi.travel/reference/post_flights-verify.md): ## Overview Confirm a flight offer is still available and retrieve the latest pricing before proceeding to booking. Always verify before prebooking to avoid price discrepancies. ## When to Use - **Pre-booking validation** - Confirm offer availability after user selects a flight - **Price confirmation** - Show users the guaranteed price before they enter payment details - **Fare rule retrieval** - Get the latest cancellation and change policies ## What You Get - **Verified pricing** with up-to-date fare breakdown - **`changes`** (when present) — cabin/fare flags, human-readable `messages`, and **`pricing`** (`old` / `new` full OfferPricing) instead of deprecated scalar currency/prices - **Journey `pricing`** — `original` (provider/PCC) and `display` (customer) price breakdown per provider FlattenedJourney - **Fare family details** including name and included amenities - **Baggage policy** for each passenger type and segment - **Booking terms** including cancellation and change fee rules ## Key Features - **Real-time price check**: Confirms current availability and price with the provider - **Updated baggage info**: Returns the latest baggage allowances at time of verification - **Fare rules**: Includes cancellation and change fee policies before commitment ## Quick Start Provide the `offerId` from `/flights/rates` search results. Use the verified offer data to populate a booking summary page before proceeding to `/flights/prebooks`. - [Flexible-date price matrix (one-way or round-trip)](https://docs.liteapi.travel/reference/searchflightsmatrix.md): ## Overview Search the cheapest fare for each departure (and, on round-trips, return) date combination across a grid of nearby dates — `±flexDays` around the dates in your request. Accepts the same `legs`-based body as `POST /flights/rates` plus optional `flexDays` (1–3, default 3). **Supported:** one-way (1 leg) or round-trip (2 legs) only. Multi-city (3+ legs) is not supported. **Not supported:** top-level `origin`, `destination`, `departureDate`, or `returnDate` — use `legs` only. ## Access Requires Flights API access and matrix enablement on your account. Matrix search is not enabled by default — contact the LiteAPI support team to request access. ## When to Use - **Flexible-date calendars** — price heatmap when the traveller can shift dates - **Cheap-date discovery** — find the lowest fare in a ±N day window before a full `/flights/rates` search - **Round-trip date pairing** — compare outbound × return combinations on one grid - **Progressive UI** — stream cells over SSE as each underlying search completes ## What You Get - **`cells`** — one entry per valid date combination, sorted by `(outboundOffset, returnOffset)` - **`cheapest`** — globally lowest-priced cell (null when nothing was priced) - **`currency`** — currency of the global cheapest cell - **`baseOutboundDate`** / **`baseReturnDate`** — the originally requested dates - **`flexDays`**, **`roundTrip`** — grid metadata - Per-cell **`price`**, **`currency`**, date offsets, and whether the underlying search was **`cached`** or **`success`** - **Margined prices** — cell `price`, `cheapest`, and `currency` include the authenticated user's rate-search margin (same as `/flights/rates`) ## Key Features - Probes `±flexDays` (1–3) around requested departure and return dates - Each underlying date pair uses normal provider caching — a later `POST /flights/rates` for a matrix date is served from warm cache - **SSE:** send header `Accept: text/event-stream` for incremental events: `matrix-start` (grid skeleton), `matrix-chunk` (one priced cell), `matrix-complete` (full sorted grid + cheapest) - Same global `filters`, `sort`, and `options` as `/flights/rates` where applicable ## Quick Start **Required:** `legs` (1 leg for one-way or 2 for round-trip, each with `origin`, `destination`, `date`), `adults` (≥ 1), `currency` **Optional:** `flexDays` (1–3, default 3), `country`, passenger counts, `filters`, `sort` **Round-trip:** two legs — outbound then return with optional `direction` `OUTBOUND` / `INBOUND`. **One-way:** one leg. After choosing a date pair from the matrix, call `POST /flights/rates` with `legs` set to those dates for full offer details. - [1. Create a checkout session (PREBOOK)](https://docs.liteapi.travel/reference/post_flights-prebooks.md): ## Overview Initiate a flight booking session by reserving the offer with the provider, creating a payment intent when you use the Stripe SDK, and discovering available ancillary services — all in a single request. ## When to Use - **Start the booking flow** once a user has confirmed their flight selection - **Collect passenger details** and initiate payment processing - **Discover add-ons** like seat selection and extra baggage before final confirmation ## What You Get - **Prebook ID** required to complete the booking at `/flights/bookings` - **Payment intent** (`transactionId`, `secretKey`) when `usePaymentSdk` is true — for Stripe SDK integration - **Credit line snapshot** (`creditLine` in the response) when you set `includeCreditBalance: true` and your account has an enabled credit line with payment bypass - **Available services** (`servicesAttachable`) including seats and baggage options - **Booking confirmation** from the provider with reservation details ## Key Features - **End-to-end prebook flow**: Verifies offer → payment setup (Stripe payment intent or credit line) → books with provider → fetches services - **Payment options**: `usePaymentSdk: true` uses the Stripe SDK. `usePaymentSdk: false` is allowed when your user has **payment bypass** (sandbox or whitelabel) and either an **enabled credit line** or a **whitelabel/CMI** checkout (no Stripe intent; complete payment via WL and call `/flights/bookings` with `payment.method: THIRD_PARTY` and `payment.token`) - **Ancillary services**: Returns attachable services (seats, baggage) that can be added before final booking - **Same shape as /book**: Uses `offerId` instead of `prebookId` ## Quick Start **Required fields**: `offerId` (from search/verify), `contact` (name, email, phone), `passengers` (with birthday, document, and name details). **Payment**: Send `usePaymentSdk: true` for Stripe (typical). Send `usePaymentSdk: false` when paying on credit line or via whitelabel/CMI (requires payment bypass); otherwise you receive a validation error. **Tip**: Use the `servicesAttachable` in the response to offer seat selection or extra baggage before calling `/flights/bookings`. - [1.2 Attach services to prebook (Optional)](https://docs.liteapi.travel/reference/post_flights-prebooks-prebookid-services.md): ## Overview Add ancillary services such as seat selection or extra baggage to an existing prebook before confirming the final booking. ## When to Use - **Seat selection** - Allow users to choose specific seats after prebook - **Extra baggage** - Let users add additional luggage allowance - **Price update** - Required when services change the total booking cost - **Voucher discount** - Optional `voucherCode` when attaching services changes the total and you need the discount reflected on the new payment intent ## What You Get - **Updated prebook** with the selected services attached - **New payment intent** (`transactionId`, `secretKey`) reflecting the updated total price (after any voucher discount) - **Same response format** as `POST /flights/prebooks` for easy integration ## Key Features - **Seat selection**: Assign specific seats to each passenger and segment - **Extra baggage**: Add checked baggage or overweight allowances - **Updated payment**: Creates a new Stripe payment intent when the prebook used Stripe (`usePaymentSdk: true`). For whitelabel/CMI prebooks (`used_custom_payment_keys`), no new intent is returned — re-charge via WL and submit a fresh JWT at `POST /flights/bookings` - **Voucher recalculation**: When a voucher applies, the discount is recomputed against the updated total (journey + ancillaries); invalid or expired vouchers return `400` (same as prebook) - **Modifies in place**: Updates the existing prebook record in the database ## Quick Start Provide the `prebookId` in the URL path and `selectedServices` in the request body. Optionally pass `voucherCode` to apply a discount. Use the **new** `transactionId` from this response (not the original prebook `transactionId`) when confirming payment with Stripe and when calling `POST /flights/bookings`. - [1.3 Get prebook details (optional)](https://docs.liteapi.travel/reference/getflightprebook.md): ## Overview Retrieve an existing flight checkout session (prebook) by ID, including any ancillary services already attached and a live catalog of remaining attachable services. ## When to Use - **Resume checkout** — Reload prebook state after the user navigates away - **Confirm attached ancillaries** — Show selected seats/bags before final book - **Reuse payment intent** — Returns the stored Stripe `transactionId` / `secretKey` as-is (GET does not create or refresh a PaymentIntent) - **Credit balance** — Optionally include a live credit-line snapshot with `includeCreditBalance=true` ## What You Get - Same core `FlightPrebookData` shape as `POST /flights/prebooks` / attach-services (journey, pricing, payment intent fields, `servicesAttachable`) - `booking.selectedServices` / `booking.bookedServices` when services were attached - Live `servicesAttachable` from the provider (not persisted) - Existing payment fields conserved from create/attach - Optional `creditLine` when `includeCreditBalance=true` (live remaining credit when the account can cover the prebook price) ## Quick Start Provide the `prebookId` returned from `POST /flights/prebooks` in the URL path. Optionally pass `includeCreditBalance=true` to include credit-line availability. - [2. Complete a booking](https://docs.liteapi.travel/reference/post_flights-bookings.md): ## Overview Complete a flight reservation by confirming a prebook and processing payment. This is the final step in the booking flow. ## When to Use - **Final booking confirmation** - Convert a prebook into a confirmed booking - **Payment completion** - Confirm with Stripe (`TRANSACTION_ID`) or bill an enabled **credit line** (`CREDIT`) - **After service selection** - Book after optionally attaching seats or baggage via the services endpoint ## What You Get - **Confirmed booking** with a unique booking ID - **Payment confirmation** with transaction details - **Full itinerary** including all segments and passenger assignments - **Provider confirmation** reference number ## Key Features - **Idempotent**: Returns the existing booking (HTTP 200 + `data[0].message`) if one already exists for the given `prebookId`. Transient book failures are retried in place without exposing a terminal failure status. Concurrent duplicate requests while a book is in progress return HTTP 409 (`45035`). - **Payments**: Stripe uses `transactionId` from prebook or attach-services after SDK confirmation; credit line uses `CREDIT` with server-side eligibility checks - **Provider confirmation**: Finalizes the reservation on the provider side ## Quick Start **Required fields**: `prebookId` (from `POST /flights/prebooks`), `payment` with `method` and, for Stripe, `transactionId` **Tip**: If you used `POST /flights/prebooks/{prebookId}/services` to attach ancillary services, use the new `transactionId` from that response, not the original prebook `transactionId`. - [Get booking details](https://docs.liteapi.travel/reference/get_flights-bookings-bookingid.md): ## Overview Retrieve complete details of a confirmed flight booking using its unique booking ID. ## When to Use - **Booking confirmation page** - Display full itinerary after booking completes - **Booking management** - Retrieve details for an existing reservation - **Itinerary display** - Show passengers, segments, and confirmation numbers - **Status checks** - Verify booking status for a given booking ID ## What You Get - **Complete itinerary** with all flight segments and connection details - **Passenger manifest** with names, documents, and seat assignments - **Booking status** and provider confirmation reference - **Pricing breakdown** including taxes and fees paid ## Key Features - **Full booking record**: Returns all data associated with the confirmed booking - **Provider reference**: Includes the provider-side booking confirmation number - **Passenger details**: Complete passenger information for all travelers ## Quick Start Provide the `bookingId` (returned from `POST /flights/bookings`) in the URL path. Returns the complete booking record. - [List bookings](https://docs.liteapi.travel/reference/get_flights-bookings.md): ## Overview List confirmed flight bookings owned by the authenticated user. Supports an optional PNR + last-name lookup for retrieving a single booking. ## When to Use - **"My bookings" page** - Display the authenticated user's confirmed flight bookings - **PNR lookup** - Retrieve a single booking by `airlinePnr` and a passenger's `lastName` - **Booking management** - Build dashboards or list views of past and upcoming reservations ## What You Get - **Confirmed bookings only** - Returns records persisted from the booking flow; - **Full booking objects** with status, journey, passengers, order reference, and pricing - **Sandbox isolation** - Sandbox and live bookings are scoped by the API key used ## Key Features - **Owner-scoped**: Only returns bookings belonging to the authenticated user - **PNR + last-name lookup**: When both `airlinePnr` and `lastName` are supplied, returns a single matching booking; both are required together - **Stable response shape**: `data` is always an array containing exactly one element with a `bookings` array ## Quick Start Call with no query parameters to list all bookings for the authenticated user. To look up a specific booking, pass both `airlinePnr` and `lastName`. - [Get cancellation quote](https://docs.liteapi.travel/reference/get_flights-bookings-bookingid-cancellations.md): ## Overview Returns refund eligibility, estimated refund amounts, and penalty details for a booking **without actually cancelling it**. Use this before calling `POST /flights/bookings/{bookingId}/cancellations` to understand the financial impact of cancellation. ## When to Use - **Pre-cancellation review** — Show the customer the potential maximum refund (not guaranteed) before they confirm cancellation - **Refund estimation** — Display potential maximum refund and penalty amounts in the booking management UI (refund is not granted until cancel completes) - **Eligibility check** — Determine whether the booking is within the void window (`isVoidable`) or eligible for a partial refund (`isRefundable`) ## What You Get - **`confidence`** — How reliable the quote is (`confirmed`, `estimated`, `heuristic`, `unknown`) - **`isRefundable` / `isVoidable`** — Quick eligibility flags - **`refund` / `penalty`** — Aggregate amounts with margin applied. `refund` is the potential maximum the airline may refund — not a granted/guaranteed amount - **`penalties[]`** — Itemised penalty breakdown when available - **`tickets[]`** — Per-ticket detail when available - **`destination`** — Where refunded money goes (`original_payment`, `agency_deposit`, `voucher`, etc.) - **`vouchers[]`** — Airline travel vouchers / credit-shells when `destination` is `voucher`; omitted when absent. Distinct from LiteAPI discount `voucherCode` on prebook ## Concurrent cancellation If a cancellation was already submitted and is still awaiting provider confirmation, this endpoint returns **HTTP 409** with code `49007` (`CONCURRENT_OPERATION`). A new quote is not available until that cancellation completes or fails. ## Refund amount caveat The `refund` amount on a cancellation quote is the **potential maximum** the airline may refund if cancellation proceeds under the quoted conditions. It is an estimate for decision-making only and is **not granted** — the final refund (if any) is determined when cancellation completes and may be lower or zero. The refund may arrive asynchronously once the airline determines the final amount. ## Key Features - **Non-destructive** — Does not cancel the booking; safe to call before user confirmation - **Margin-applied pricing** — All amounts (including voucher `pricing.display`) reflect the same margin applied at booking time ## Quick Start Provide the `bookingId` from `POST /flights/bookings` in the URL path. Every call hits the upstream provider — do not place this on a hot polling loop. - [Cancel a booking](https://docs.liteapi.travel/reference/post_flights-bookings-bookingid-cancellations.md): ## Overview **Cancels a flight booking.** Submits cancellation for an existing booking and returns the cancellation outcome. Call `GET /flights/bookings/{bookingId}/cancellations` first to preview the financial impact without committing. If cancellation is accepted but not yet confirmed, this endpoint returns **HTTP 202** with `status: CONFIRMED` (the booking is unchanged until the airline finalizes). Retries while cancellation is still pending are idempotent. While cancellation is awaiting confirmation, a subsequent `GET /flights/bookings/{bookingId}` includes `cancelIntentAt` (timestamp of the cancel request). When cancellation completes, the response is **HTTP 200** with a final status of `CANCELLED` or `CANCELLED_WITH_CHARGES`. All asynchronous cancellation updates are delivered as webhook events — subscribe to flight booking webhooks to receive final confirmation and status changes. ## When to Use - **Confirmed cancellation** — Cancel the booking with the airline after the cancel quote has been reviewed and agreed ## What You Get - **`bookingId`** — The LiteAPI booking identifier - **`status`** — Current booking status: `CONFIRMED` while cancellation is awaiting airline confirmation (HTTP 202), or final `CANCELLED` / `CANCELLED_WITH_CHARGES` (HTTP 200) - **`cancellation_fee`** — Total cancellation penalty; often `0` on idempotent pending retries - **`refund_amount`** — Amount to be returned (if any) - **`currency`** — Currency of the fee and refund amounts - **`destination`** — Where refunded money goes (`original_payment`, `agency_deposit`, `voucher`, etc.) - **`vouchers[]`** — Airline travel vouchers when issued in lieu of cash; omitted when absent ## Key Features - **Hotel-parity response** — Flat `data` object with `bookingId`, `status`, `cancellation_fee`, `refund_amount`, `currency`, plus optional `destination` / `vouchers` - **Pending cancel intent** — HTTP 202 when the airline accepts the cancel but has not confirmed it yet; booking stays `CONFIRMED` until cancellation is finalized, and `GET /flights/bookings/{bookingId}` returns `cancelIntentAt` - **Fee-based final status** — When cancellation completes (HTTP 200), the final `status` depends on `cancellation_fee`: if the fee is `0`, the booking is fully cancelled (`CANCELLED`); if the fee is greater than `0`, the booking is cancelled with charges retained (`CANCELLED_WITH_CHARGES`) ## Quick Start Provide the `bookingId` from `POST /flights/bookings` in the URL path. No request body is required. - [Get booking services](https://docs.liteapi.travel/reference/get_flights-bookings-bookingid-services.md): ## Overview Retrieve the ancillary services (seats, baggage) for an existing flight booking: services that are **already booked** together with the live catalog of services that **can still be booked**. ## When to Use - **Post-booking upsell** - Show the passenger which seats and bags they can still add after the booking was created - **Booking management** - Display the services already attached to the booking with the prices that were charged - **Availability refresh** - The bookable catalog is fetched live from the provider on every call ## What You Get - **`groups`** - Bookable services grouped by category (seat, baggage) with post-margin prices and encoded `serviceId`s - **`bookedServices`** - Services already attached to the booking; entries booked through the API carry the exact price that was charged at attach time - **`expiresAt`** - Validity window of the bookable catalog ## Key Features - **Read-only**: Safe to call at any time; the catalog reflects live availability - **Consistent pricing**: Booked services echo the post-margin amounts the user actually paid ## Quick Start Provide the `bookingId` (returned from `POST /flights/bookings`) in the URL path. > **Note:** Booking additional services on an existing booking is not available yet; this endpoint currently only reports availability. - [Precharge extra charges on a booking](https://docs.liteapi.travel/reference/prechargeflightextracharges.md): ## Overview Creates a pending post-booking extra-charge batch for an existing flight booking and returns an opaque `chargesId`. For Stripe-paid bookings, also creates a PaymentIntent (`transactionId` + `secretKey`) when `usePaymentSdk` is true. ## Access Requires Flights API access. Post-booking extra charges are not enabled by default — contact the LiteAPI support team to request access. ## When to Use - Attach fees after confirmation (seat change, baggage, admin adjustment) - Obtain a Stripe client secret so the customer can confirm payment before `POST .../extra-charges/charges` ## What You Get - **`chargesId`** — Opaque token required by `/extra-charges/charges` (do not re-send charge lines) - **`paymentTypes`** — Locked to the booking's original payment (`TRANSACTION_ID` or `CREDIT`) - **`transactionId` / `secretKey`** — Present for Stripe bookings when `usePaymentSdk` is true - Existing extras totals plus pending batch totals ## Constraints - Booking status must be `CONFIRMED` or `PENDING_CONFIRMATION` - All lines in one request must share the same currency - Payment method on `/charges` must match the original booking payment - [Confirm extra charges on a booking](https://docs.liteapi.travel/reference/chargeflightextracharges.md): ## Overview Confirms a pending extra-charge batch created by `/extra-charges/precharges`. Captures the Stripe PaymentIntent or bills the credit line, then appends the lines to the booking. ## Access Requires Flights API access. Post-booking extra charges are not enabled by default — contact the LiteAPI support team to request access. ## Idempotency Idempotent on `chargesId`, mirroring `POST /flights/bookings` prebookId replay: - **Already confirmed** — HTTP 200 with `data.message` and the persisted extras (no re-capture / no duplicate credit-line billing) - **Concurrent confirm** — HTTP 409 / `45035` while another confirm for the same `chargesId` holds the Redis lock; retry after the first completes ## When to Use - After the customer confirmed the Stripe PaymentIntent (status `requires_capture` / `succeeded`), or immediately for `CREDIT` bookings ## Constraints - Body only needs `chargesId` + `payment` (charge lines are encoded in `chargesId`) - `payment.method` must match the booking's original payment (`TRANSACTION_ID` or `CREDIT`) - For Stripe, `payment.transactionId` must be the id returned by precharges - [Match supplier rooms to a reference catalog](https://docs.liteapi.travel/reference/post_rooms-match.md): ## Overview Match supplier room names to your reference catalog. For each supplier room, returns the best matching reference room along with ranked alternatives and confidence scores. ## When to Use - **Normalize supplier inventory** - Map diverse supplier room names to your canonical catalog - **Rate shopping** - Identify equivalent rooms across suppliers for price comparison - **Content enrichment** - Link supplier rooms to your reference data for consistent display - **Booking flows** - Ensure supplier rooms match expected room types before confirmation ## What You Get - **Match status** - `mapped` or `not_mapped` for each supplier room - **Best match** - Reference room with highest confidence (when above threshold) - **Ranked candidates** - Top K alternative matches with scores - **Confidence scores** - How confident the match is (0-1) ## Quick Start **Required fields**: `references` (your catalog rooms), `suppliers` (rooms to map) **Optional tuning**: Set `threshold` (default 0.5) for match sensitivity, `topK` (default 3) for number of candidates - [Submit an async room mapping job](https://docs.liteapi.travel/reference/post_rooms-match-async.md): ## Overview Submit an async room mapping job for a hotel. The job processes in the background and produces high-quality mappings with detailed reasoning for each decision. Only one job per hotel can run at a time. **Note:** Internally referred to as a deep-map job. ## When to Use - **Batch processing** - Map large sets of supplier rooms for a hotel - **Initial hotel setup** - Establish canonical mappings when onboarding a property - **Periodic refresh** - Re-map rooms when supplier catalogs change ## What You Get - **Job ID** - Unique identifier to poll for results - **Queued status** - Immediate confirmation that processing has started - **Background processing** - Results ready in seconds to minutes ## Quick Start **Required fields**: `hotelId`, `referenceRooms` (your catalog, max 500), `roomNames` (supplier names to map, max 100) **Poll for results**: Use `GET /rooms/match/async/jobs/:jobId` until status is `completed` or `failed` - [Get async room mapping job status](https://docs.liteapi.travel/reference/get_rooms-match-async-jobs-jobid.md): ## Overview Check the status of an async room mapping job and retrieve results. Returns full job details including per-room decisions when complete. Jobs expire 24 hours after completion. ## When to Use - **Poll for completion** - Check job status until `completed` or `failed` - **Retrieve results** - Get mapping decisions with reasoning for each room - **Review changes** - See what changed from prior cached mappings - **Debug issues** - Inspect why specific rooms were mapped or rejected ## What You Get - **Job status** - `queued`, `running`, `completed`, or `failed` - **Mapping results** - Final decision for each room with confidence - **Previous vs final** - Compare with prior mappings - **Rejection reasons** - Why unmapped rooms were rejected - **Actions taken** - `confirm`, `remap`, `reject`, or `keep_existing` ## Quick Start **Required**: `jobId` path parameter from the POST response **Poll interval**: 5-10 seconds recommended - [Get saved room mappings for a hotel](https://docs.liteapi.travel/reference/get_rooms-match-async-matches-hotelid.md): ## Overview Retrieve all saved room mappings for a hotel. Returns the current mapping cache without job details or audit trail. ## When to Use - **Lookup existing mappings** - Check what mappings already exist for a hotel - **Runtime resolution** - Resolve supplier room names to reference rooms during booking - **Cache inspection** - View all mappings after async jobs complete - **Integration sync** - Pull current mappings into external systems ## What You Get - **Hotel ID** - Confirmed hotel identifier - **Mappings dictionary** - Keyed by normalized supplier name - **Final decisions** - Reference room name, ID, and confidence - **Rejection reasons** - Why unmapped rooms were rejected ## Quick Start **Required**: `hotelId` path parameter **Note**: Returns the full hotel cache from all previous jobs. For job-specific results with audit trail, use the Get async room mapping job status endpoint. - [Group rooms without a reference catalog](https://docs.liteapi.travel/reference/post_rooms-group.md): ## Overview Group similar room listings for a property without needing a reference catalog. Automatically clusters rooms based on attributes like room class, bed type, and view. ## When to Use - **No reference catalog** - Cluster rooms when you don't have a canonical room list - **Multi-supplier aggregation** - Group equivalent rooms across different suppliers - **Deduplication** - Identify duplicate or near-duplicate room listings - **Content analysis** - Extract structured attributes from room names ## What You Get - **Room groups** - Clusters with `groupCode`, `groupName`, and member rooms - **Unmapped rooms** - Rooms that couldn't be grouped - **Display names** - Suggested names for each group - **Parsed attributes** - Extracted room details (when `debug: true`) ## Quick Start **Required fields**: `propertyId`, `propertyName`, `supplierList` with rooms **Customize grouping**: Set `parameters.outputAggregation` to control which attributes form groups (default: `roomClass`, `roomType`, `bedType`, `roomView`) - [Group rooms into reference buckets](https://docs.liteapi.travel/reference/post_rooms-group-with-reference.md): ## Overview Assign supplier rooms to reference room buckets. Each supplier room is placed under its best-matching reference room (exclusive assignment - one group per supplier). ## When to Use - **Catalog-based grouping** - Assign suppliers to your normalized reference rooms - **Bulk bucketing** - Quickly categorize many supplier rooms by reference - **Strict assignment** - Ensure each supplier maps to exactly one reference (or none) - **Quality control** - High default threshold (0.8) ensures confident assignments ## What You Get - **Groups by reference** - Each reference with its assigned supplier rooms - **Match counts** - Number of suppliers per reference group - **Unmatched suppliers** - Rooms that didn't meet threshold for any reference ## Quick Start **Required fields**: `references` (your catalog buckets), `suppliers` (rooms to assign) **Threshold tuning**: Default 0.8 is strict; lower for more matches, raise it for higher precision - [List eSIMply destinations](https://docs.liteapi.travel/reference/getesimplydestinations.md): ## Overview Retrieve the list of countries and regions where eSIM data packages are available. Use this as the entry point for destination pickers in your app or website. ## When to Use - **Destination picker** - Populate a list of countries travelers can buy eSIM coverage for - **Featured destinations** - Highlight featured or package destinations in marketing UI - **Localized catalogs** - Request English or French destination names with `lang` ## What You Get - **Destination list** - ISO codes, display names, flags, and cover images - **Grouped destinations** - Optional grouped catalog entries for multi-country packages - **Feature flags** - `isPackage` and `isFeatured` for UI prioritization ## Key Features - **Language support**: Optional `lang=en|fr` for localized names - **Sandbox vs production**: `sand_*` keys hit the eSIMply sandbox; `prod_*` keys hit production - **Access control**: Requires `esimply_access` enabled on the partner account - [List packages for a destination](https://docs.liteapi.travel/reference/getesimplypackagesbydestination.md): ## Overview Retrieve available eSIM data packages for a specific destination, including data size, validity, and pricing. ## When to Use - **Package selection UI** - Show travelers the plans available for a chosen country - **Price display** - Present selling prices in the traveler's preferred currency - **Inventory checks** - Confirm which packages can be added to a cart ## What You Get - **Package catalog** - Name, data size (MB), validity days, and package IDs - **Pricing** - `calculatedPrice`, optional `b2bPrice`, and `currency` - **Destination branding** - Flag URL for UI display ## Key Features - **Currency conversion**: Optional `Currency` header converts prices via liteAPI FX rates - **Destination-scoped**: Pass the destination ISO2/code from the destinations list - **Ready for cart**: Use `packageId` with create-cart to start a purchase - [Create an eSIMply cart](https://docs.liteapi.travel/reference/createesimplycart.md): ## Overview Initialize a shopping cart for a selected eSIM package and travel dates. The returned `cartKey` is required to submit the purchase. ## When to Use - **Start checkout** - After the traveler selects a package and travel window - **Hold a package** - Create a short-lived cart before collecting traveler details - **Multi-step flows** - Separate package selection from payment/provisioning ## What You Get - **Cart key** - Opaque `cartKey` used by submit order ## Key Features - **Date-bound**: Requires `startDate` and `endDate` for the travel period - **Package-scoped**: Uses `packageId` and `destinationCode` from the catalog - **Idempotent submit later**: Reuse the same `cartKey` safely when submitting - [Submit an eSIMply order](https://docs.liteapi.travel/reference/submitesimplyorder.md): ## Overview Finalize a cart and provision the eSIM. On success you receive the order ID, ICCID, QR / LPA install payload, and purchase details. Successful orders are persisted for the partner account. ## When to Use - **Complete purchase** - After collecting traveler contact details - **Provision eSIM** - Generate installable QR / activation data for the traveler - **Partner reconciliation** - Attach your `clientReference` for support and reporting - **Safe retries** - Resubmit the same `cartKey` after timeouts; liteAPI returns the stored order without buying again ## What You Get - **Order ID** - Provider order identifier - **Purchases** - ICCID, QR code, SM-DP address, activation code, package and pricing - **Traveler-ready install data** - Everything needed to install the eSIM on a device ## Key Features - **Idempotent by cartKey**: Retrying submit with an already-completed `cartKey` returns the persisted order - **Currency conversion**: Optional `Currency` header converts priced fields via liteAPI FX - **End-user details required**: Email, phone, first and last name - **Persistent records**: Successful submits are stored in liteAPI (`esimply_orders` / `esimply_purchases`) - [List eSIMply orders](https://docs.liteapi.travel/reference/getesimplyorders.md): ## Overview Retrieve eSIM order history for the authenticated partner account, with optional filters for destination, date range, and client reference. ## When to Use - **Partner dashboard** - Show past eSIM purchases and top-ups - **Support lookup** - Find orders by destination or your `clientReference` - **Reporting** - Pull order history for a travel date window ## What You Get - **Order records** - Packages, ICCIDs, pricing, destinations, install metadata, and plan `status` (`active` or `expired`) - **Filterable history** - Narrow results by destination, dates, or client reference ## Key Features - **Flexible filters**: `destination`, `startDate`, `endDate`, `clientReference` - **Currency conversion**: Optional `Currency` header for priced fields - **Environment-aware**: Sandbox and production histories are separate by API key - [List top-ups for an eSIM](https://docs.liteapi.travel/reference/getesimplytopups.md): ## Overview Retrieve top-up packages that can be applied to an existing eSIM identified by ICCID. ## When to Use - **Top-up UI** - Show add-on data packs for a traveler's active eSIM - **Upsell after purchase** - Offer more data when usage is low - **Eligibility check** - Confirm which packages are valid for a given ICCID ## What You Get - **Top-up packages** - Package IDs, sizes, validity, and prices - **External package IDs** - Required when submitting a top-up ## Key Features - **ICCID-scoped**: Returns only packages eligible for that eSIM - **Currency conversion**: Optional `Currency` header for priced fields - **Feeds POST /esimply/orders/submit-topup**: Use returned IDs in the top-up submit request - [Submit an eSIMply top-up](https://docs.liteapi.travel/reference/submitesimplytopup.md): ## Overview Apply a top-up package to an existing eSIM in a single request. On success you receive an order response with updated purchase details. Successful top-ups are persisted for the partner account. ## When to Use - **Add more data** - Traveler needs additional MB on an existing eSIM - **Extend connectivity** - Apply a package without issuing a new ICCID - **Safe retries** - Resubmit with the same `Idempotency-Key` after network failures ## What You Get - **Order ID** - Provider order identifier for the top-up - **Purchase details** - Updated package, pricing, and eSIM identifiers ## Key Features - **Idempotency**: Required `Idempotency-Key` header for safe retries - **Currency conversion**: Optional `Currency` header for priced fields - **Persistent records**: Successful top-ups are stored in liteAPI - [Get an eSIMply order by ICCID](https://docs.liteapi.travel/reference/getesimplyorderbyiccid.md): ## Overview Retrieve a single eSIM order (purchase details, install metadata, and plan status) using its ICCID. ## When to Use - **Order detail page** - Show one eSIM's package, pricing, and QR install data - **Customer support** - Look up a traveler's eSIM by ICCID - **Re-display QR** - Recover LPA / activation details after purchase ## What You Get - **Full order record** - Package, destination, prices, ICCID, QR, SM-DP, activation code, and `status` (`active` or `expired`) - **Lifecycle dates** - Created, start, and end timestamps when available ## Key Features - **ICCID lookup**: Direct access without scanning the full order list - **Currency conversion**: Optional `Currency` header for priced fields - **Not found handling**: Returns a not-found error when the ICCID is unknown - [Get eSIM data usage by ICCID](https://docs.liteapi.travel/reference/getesimplydatausagebyiccid.md): ## Overview Retrieve live data usage for an eSIM: remaining allowance, total allowance, expiry, and status. ## When to Use - **Usage meters** - Show travelers how much data remains - **Top-up prompts** - Trigger upsell when remaining data is low - **Status checks** - Confirm whether an eSIM is still active ## What You Get - **Remaining / total** - Data volumes in MB - **Expiry** - When the current allowance expires - **Status** - Current eSIM usage status ## Key Features - **Live provider data**: Usage is fetched from eSIMply for the given ICCID - **Lightweight**: No pricing or catalog payload—usage only - **Pairs with top-ups**: Use remaining data to decide when to offer top-ups - [Rate Limiting](https://docs.liteapi.travel/reference/rate-limiting.md): To ensure fair use of resources, Nuitee Connect enforces rate limits on API requests. If you exceed the rate limits, you will receive a "429 Too Many Requests" response. - [Error handling](https://docs.liteapi.travel/reference/error-handling.md): Nuitee Connect uses standard HTTP status codes to indicate the success or failure of an API request. - [SDKs](https://docs.liteapi.travel/reference/sdks.md): Install a Nuitee Connect SDK, pass your API key, and call search, prebook, and book without hand-rolling every HTTP request. - [Node.JS](https://docs.liteapi.travel/reference/nodejs-sdk.md): This guide will help you get started with integrating the Nuitee Connect SDK into your Node.js application. - [Python](https://docs.liteapi.travel/reference/python.md) - [API Errors for booking workflow](https://docs.liteapi.travel/reference/api-errors-for-hotel-booking-workflow.md): Error codes returned by the hotel booking flow: search rates, prebook, and book. - [Languages for content](https://docs.liteapi.travel/reference/languages-for-content.md): https://docs.liteapi.travel/reference/get_data-languages - [Currencies](https://docs.liteapi.travel/reference/currencies-1.md): https://docs.liteapi.travel/reference/get_data-currencies - [Room Views](https://docs.liteapi.travel/reference/room-views.md) - [Room Amenities](https://docs.liteapi.travel/reference/room-amenities.md) - [Get weather data](https://docs.liteapi.travel/reference/get_data-weather.md): ## Overview Get weather forecasts for specific locations. Response structure adapts based on the forecast time range (short-term vs. long-term). ## When to Use - **Travel planning** - Show weather forecasts for destinations - **Hotel pages** - Display weather information on hotel detail pages - **Trip preparation** - Help users plan for weather conditions - **Destination information** - Provide weather context for locations ## What You Get - **Weather forecasts** - Temperature, humidity, wind, precipitation - **Time-based structure** - Different formats for short-term (<1 week) vs. long-term forecasts - **Detailed data** - Atmospheric pressure, conditions, and summaries - **Date-specific** - Weather data for specific dates ## Key Features - **Adaptive structure** - Response format changes based on time range - **Short-term** - Detailed hourly/daily data for forecasts within one week - **Long-term** - Daily summaries for forecasts beyond one week - **Accuracy note** - Forecasts beyond one week have reduced accuracy ## Quick Start Provide location coordinates (`latitude`, `longitude`) and date range. Returns weather forecasts with appropriate detail level. ## Pages - [Postman collection for Nuitee Connect v3](https://docs.liteapi.travel/page/postman-collection.md)