Post booking: Reporting and cancelling Third Party Inventory (TPI) bookings

Learn how to gerate accurate, efficient reporting on bookings with TPI Net and Commissionable (Sell) rates, and how to cancel TPI bookings if needed.

Post booking TPI rates reporting

This section of the guide explains how to identify third-party bookings and distinguish between Net and Commissionable sell rate transactions in your reporting and aims to help you consolidate all relevant booking data, distinguish rate types, and align with Booking.com transactional reports — without the need for manual or event-triggered API calls.

Reporting endpoints

After a booking is completed, you can use the orders/details and orders/details/accommodations endpoints to retrieve details for all stays transactions, including:

✅ Regular bookings from Booking.com inventory.

✅ Third Party Inventory (TPI) bookings: Both net and sell rates (if activated for your account).

Using orders/details and orders/details/accommodations

The orders/details and orders/details/accommodations endpoints work together to provide a complete picture of your bookings:

Together, orders/details and orders/details/accommodations endpoints give you complete visibility of all bookings — from Booking.com and third-party inventory — and reliable inputs for your reporting processes.

Identifying TPI products in the response

Both endpoints response objects include an inventory field with details about the source of the product:

Consolidated reporting for all stays bookings

When you use the orders/details endpoint without specifying order IDs, but setting a specific period of time, all your stays bookings are returned, including:

• Direct bookings (from Booking.com inventory).
• TPI bookings with net rates.
• TPI bookings with sell rates.

This helps you maintain a consolidated view of all transactions.

You can apply filtering in your system to focus on specific subsets of data for your reporting needs.

Suggested reporting flow

We recommend automating scheduled API calls and applying filtering to efficiently retrieve only the bookings relevant for your reporting and reconciliation processes.

Step 1 - Schedule API calls

Automate API calls to both endpoints based on your reporting needs:

Adjust the frequency based on your reporting needs — daily is recommended for operational reporting, weekly for financial reconciliation.

Step 2 - Filter bookings in your requests

For efficient reporting:

• Use the "end" parameter in your requests, to retrieve only those bookings that have already finished (based on checkout date) and with status "stayed" — this ensures you only report on transactions linked to completed stays.
• Alternatively, filter by creation date to target bookings within a specific period.

Example of orders/details request with "end" parameter:

{
  "end": {
    "from": "2025-03-01",
    "to": "2025-03-07"
  },
  "currency": "EUR",
  "maximum_results": 20,
  "sort": {
    "by": "updated",
    "direction": "descending"
  },
  "extras": [
    "payment"
  ]
}

After retrieving the response, filter in your system all results where third_party_inventory: true to focus only on TPI bookings.

Step 3 - Distinguish between net and sell rates

The inventory.type field indicates the rate type for each booking:

• "net" — Net rate transaction (non-commissionable)
• "sell" — Sell rate transaction (commissionable)

Step 4 - Map bookings to your transactional reporting

Cross-reference booking data from these endpoints with Booking.com’s transactional reports for consistency.

We recommend storing booking details in your internal reporting system, for example:

Step 5 - Recommended automation setup

To minimise manual work and ensure reporting accuracy:

• Trigger API calls to both endpoints after each booking confirmation or based on checking/checkout dates (started or end).
• Store third_party_inventory: true and inventory.type in your internal booking database.
• Reconcile daily or weekly with Booking.com’s transactional reports daily or weekly.
• Exclude net rate transactions from Credit Slip reconciliation.

Cancelling a TPI booking

TPI bookings follow the cancellation policies defined by the product.

→ Use the standard /orders/cancel endpoint when allowed.

Always check the cancellation policy before attempting cancellation.

• In accommodation/availability response under policies.cancellation.type
• In orders/preview response looking at the cancellation schedule (from).

Next steps

Learn more about how TPI works across different business models:

Sell rates guide

Learn everything about Sell rates, benefits, and specific use cases.

Read now

Net rates guide

Learn about Net rates benefits, best practices and specific use cases.

Read now