ACTIVITIES
The objective of this document is to describe the flow of searching and purchasing activities.
The Activities API is divided into two categories: ‘Ticket’ and ‘Tour’.
- The ‘Ticket’ category refers to park tickets in Orlando
- The ‘Tour’ category covers other activities and tickets.
Api Services
| Section | Description |
|---|---|
| Discovery | Returns the inventory of activities available for the specified destination.s |
| Modalities | Provides detailed information about the ticket based on the type of ticket being queried. |
| Availability | Verifies the availability and price of the ticket being searched for on a specific date. |
| Shopping | Returns the available modalities for a theme park product, including pricing and availability within the requested date range. |
Flow
Step-by-step flow
sequenceDiagram
Actor Partner
participant Discovery as /Discovery
participant Modalities as /Modalities
participant Availability as /Availability
participant BookingFlow
Partner->> Discovery: destination + site + language
Discovery-->> Partner: 'available_tickets'
Partner->> Modalities: id (tracking_id) + site
Modalities-->>Partner: ticket/tour details
Partner->> Availability: id + modality + date + site + language + schedule (tours)
Availability-->> Partner: choice_id
Partner->>BookingFlow: choice_id
Step 1 — Modalities
Enter with the park id. You can optionally pass a date to narrow down the response, but it's not required. The response returns all available modalities for that park, each with a reference price. Use this to let the user browse and select the option they want.
Step 2 — Availability
Once a modality is selected, call availability with the target date and the passenger distribution. The response returns the final price for that specific date and configuration.
Repeat this call for each date you want to check — one request per date.
Shopping flow
Entry point
The id parameter accepts a theme park identifier. Currently supported values: DY_ORL, UN_ORL, SW_ORL, BG_ORL. To filter results to specific modalities, pass them explicitly — otherwise the response includes all modalities available for that park.
Date range
from is required. The maximum search window is 7 days, counting the start date.
- If you don't pass to, the API defaults to from + 6 days (a full 7-day window).
- If to is more than 7 days from from, the API returns only the first 7 days.
- If to is within 7 days, the API returns exactly the days requested.
Response structure
The response contains an array of modalities. Each modality contains one entry per day, exposing the availability status and final price for that date.
Updated about 1 month ago