Searching for activity availabilities

Once you have identified a specific activity you can search for available timeslots.

Since timeslots are shown only for a given date, the first step is to find a suitable specific day and then drill down.


You only see what's available

Please note

  • date/time-slots that are no longer available are not listed in our API.

Search for dates

Usually you provide your user a calendar from which to pick a day.
Not all days offer, however, availability.
Using this endpoint you can manage to provide an "intelligent" user interface where you can you to choose from only the available dates.

GET {{api_base_url}}/activities/{uuid}/dates











Example with parameters:
GET {{api_base_url}}/activities/{uuid}/dates?date_from=YYYY-MM-DD&date_to=YYYY-MM-DD

Look for availabilities

Once you have found the day, the next step is to search for all available tickets for that day. Please note that the same activity can have different types of tickets (called holders) for different days.
For instance, an activity can have "Adult" and "Child" ticket for one day and only an "Adult" ticket for another.

To do so, you can use the endpoint:
GET {{api_base_url}}/activities/{uuid}/dates/YYYY-MM-DD

Using the data in the response, you must create an interface that allow the customer to select the Group, the Product, the Time, and the Language (if any).

The combinations of these data let you find the product_id, which is the main piece of information needed to create the cart.

The response is a collection of items under the key groups containing:

name : This refers to the options you can pick for an activity. Possible values are Entrance, Entrance with audioguide, Tour with lunch etc. The value of this field is related to the value of Accept-Language header.

feature_code: is the unique code for the feature. There is always a feature_code resulted for all our activities.

default: If true, this is the price to be considered as default among feature_code available. You should pre-select this field in your application.

slots: A collection of entrance slots available.



If an activity endpoint returns “Daily” : “true” then you shouldn’t consider the “slots” returned here since there is no time restriction in this case.


time: Time of the event. In local time.

languages: Languages available for the activity. Usually available only for activities with a guide. The list of languages can be different from one slot to another because a tour can be available in French at 14:00 and in French and Italian at 15:00.

products: A collection of products for this group/slot.


name: The holder_name of the participant. Possible values are Adult, Child, Teacher etc. The value of this field it related to the value of Accept-Language header.

holder_code: The unique code for the name. There is always a holder_code resulted for all our activities.


default: If true, this product has to be considered as default.

product_id: The unique identifier of the product.

min_buy: Min number of buyable tickets.

max_buy: Max number of buyable tickets.

raw_price/discount_amount/retail_price: The value presented to the user is retail_price. The values of these fields change depending on the value of the X-Musement-Currency header.