Cutoff and confirmation times
Whenever possible, Musement strives to offer activities with same-day availability and instant confirmation. However, activity providers may need more time to process a booking request.
The /activities/{activityUuid}
endpoint contains two properties which affect an activity's availability and whether it can provide instant confirmation:
-
cutoff_time
-
max_confirmation_time
cutoff_time
The cutoff_time
property is a time range where the activity will always be unavailable. Dates that fall within the time range do not appear in the /activities/{activityUuid}/dates
endpoint.
In the example response below, no dates are available for the next seven days:
{
[...]
"max_confirmation_time": "P0D",
"cutoff_time": "P7D",
[...]
}
A value of P0D
means there is no cutoff time and the activity can provide same-day bookings, provided there is still availability.
max_confirmation_time
The max_confirmation_time
is used for activities which do not offer instant confirmation. It indicates the maximum amount of time an activity provider needs to process a booking request. During this period, a booking is not considered confirmed. Depending on the activity and the provider, the request might be accepted or rejected.
In the example response below, the provider needs two days to review a booking request:
{
[...]
"max_confirmation_time": "P2D",
"cutoff_time": "P4D",
[...]
}
The max_confirmation_time
will always be less than or equal to the cutoff_time
.