Rapid Activities API pilot documentation
Early access preview
This documentation is part of an early access preview initiative for selected partners only. Pilot programs will launch by Q3 2025, with general availability in 2026.
If you are interested in becoming a pilot or beta partner, please reach out to your account manager.
Recent evidence suggests that travelers are increasingly looking for authentic experiences over material possessions and, while this was the case pre-Covid, it's even more so in a post-pandemic world. The Rapid Activities API is designed to help partners surface activities and experiences to their customers via an easy to integrate end-to-end booking path. This allows customers to have a more holistic booking experience as well as unlock new revenue sources for partners.
The Rapid /activities API bundle
Rapid Activities is made up of a selection of endpoints that together enable a search-to-book flow.
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.
Below are the main endpoints involved:
| Action | Method | Rest URI | Result |
|---|---|---|---|
| Search for activities | GET | /activities/availability | Retrieves available activities and experiences based on a given location and date range. |
| Look at details | GET | /activities/{activity_id}/offers | Finds offers for the selected activity. Returns the times and prices for tours etc. available for that particular activity. |
| Confirm price | GET | /activities/{activity_id}/offers/{offer_id} | Returns a summarized price and required booking fields. |
| Register a payment method for the booking | POST | /payments | Registers a payment method when making a booking. The response will include a payment_token which goes in the body of the create booking request. |
| Create the booking | POST | /itineraries/activity | Create the booking. This endpoint will return an itinerary_id with relevant operation links. |
| Request details of an existing booking by itinerary ID | GET | /itineraries/{itinerary_id}/activity | Returns itinerary details by the itinerary_id parameter. |
| Request details of an existing booking by activities vendor. | GET | /itineraries/activity | Returns the details of a booking based on the affiliate_reference parameter. |
| Cancel booking | DELETE | /itineraries/{itinerary_id}/activity | Cancels an existing booking. |
Use case
Here's how you can use the Rapid Activities API to create an end-to-end booking experience for your customers.
Step 1 - Search available activities and experiences for the desired location
Use the /activities/availability endpoint to allow travelers to see what activities are available at their destination during their stay.
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 |
Step 2 - Get details of available offers for the desired activity
Get more information for the customer on what offers are available for the activity selected. The /activities/{activity_id}/offers endpoint returns the times and prices for things like tours available for the activity.
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. |
Step 3 - Confirm the price and provide payment details
Once your customer has found the perfect vacation experience, use the /activities/{activity_id}/offers/{offer_id} endpoint to validate the current pricing and required booking information.
Step 4 -Get information from the customer 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.
Step 5 - Create the booking
Use the /itineraries/activity endpoint to create a booking. This endpoint will return an itinerary_id with all the relevant operation links.
Step 6 - Retrieve booking details
You can use the /itineraries/{itinerary_id}/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.