Rapid Activities API overview
Empower your customers to book authentic things to do with the Rapid Activities API.
Early access preview
This documentation is part of an early access preview initiative for selected partners only. Pilot programs will launch by Q4 2025, with general availability in 2026.
If you are interested in becoming a pilot or beta partner, please reach out to your account manager.
The Rapid Activities API is designed to help you surface activities and experiences to travelers via an easy to integrate end-to-end booking path. This provides travelers a more holistic booking experience while allowing you to unlock new revenue sources.
Building your activities booking flow
The steps outlined below give an overview of integrating with the Activities API and building your booking path. The Rapid Activities API is made up of a selection of endpoints that together enable a search-to-book flow.
Note: Because this product is still in the early access phase, please bear in mind that the schema details and functionality are still in active development and may change before the full release of this product to partners.
1. Search available activities
The availability endpoint retrieves available activities and experiences based on a given location and date range.
Have a look at the key parameters below:
| Key parameter | Description | Recommendation |
|---|---|---|
start_date | The start date for searching for available activities. | Use ISO 8601 format. For example, 2018-02-12. |
end_date | The end date for searching for available activities. | Use ISO 8601 format. For example, 2018-02-12. |
currency | Requested currency for the rates. | Use ISO 4217 format. For example, USD. |
language | Desired language for the response. | Use only ISO639-1 alpha 2 language codes and ISO3166-1 alpha 2 country codes. |
country_code | The country code of the traveler's point of sale. | Use ISO 3166-1 alpha-2 format. This should represent the country where the shopping transaction is taking place. For example, US. |
region_id | The location or area where the traveler is looking for activities. | For example, 1122931. |
limit | The maximum number of activities returned in the response. | Maximum: 100 |
2. View offers for a chosen activity
The offers endpoint provides the traveler with more details on what offers are available for their chosen activity including times, prices, and tour availability.
Here's the kind of details travelers need to know before they book:
| Endpoint | Use it to... |
|---|---|
callouts | Provide customers with important information to know about the activity before booking. |
inclusions | Give an outline of all the features included with the activity. |
exclusions | Provide a list of features not included with the activity. |
3. Check price and provide payment details
Once the traveler has found the perfect vacation experience, use the offer_id endpoint to check pricing and required booking information.
4. Get information from the traveler on their chosen payment method
You can now use the payments endpoint to allow the customer to register a payment method for the booking. The response will contain a payment_token, which goes in the body of the create booking request.
5. Create the booking
Use the activity endpoint to create a booking. This endpoint will return an itinerary_id with all the relevant operation links.
6. Retrieve booking details
You can use the activity endpoint to retrieve booking details using the itinerary ID. The response will include cancellation links, where applicable.
API details
Explore the activity-related endpoint definitions on this page, then use a testing software to get an understanding of how the examples and schema definitions compare to the actual output. When this API is past the pilot stage, its endpoints will be included in our API Explorer as well.