Guides
Start typing to search…

ACTIVITIES

In order to certify your connection to our service, you must provide evidence of how this information is displayed on your website.

To certify your connection to our activities service, you must provide evidence of how this information is displayed on your website. The evidence must be submitted as a PDF file with clearly labeled screenshots corresponding to their item numbers and respective logs. Links to your website are not valid for this process.

Reservations for certification must be created in the Sandbox environment.

Some fields may or may not contain information depending on the case. However, they must still be considered in the integration. Some examples: additionals, exclusions, disclaimers (Prebook), etc.

A - Mandatory reservations for certification

You must create the following test reservations in our Sandbox environment:

  • By Ticket Modality available:
    • SW_ORL
    • UN_ORL
    • DY_ORL
  • By Passenger Composition:
    • Adults - 2 adults (11 and 26 years old)
    • Family - 2 adults + 2 children (5 and 9 years old)
    • With infant - 2 adults + 1 child (7 years old) + 1 infant (1 year old)

B - Full Booking Flow

ACTIVITIES SEARCH FLOW

  1. Step 1: Search (/Ticket)
    1. Verify correct implementation of the search for available tickets
    2. Confirm that all available ticket types are displayed and stored in the result.
  2. Step 2: Modalities (/Modalities)
    1. Verify that specific ticket details are obtained based on ticket_id
    2. Validate correct display of available modalities
    3. Confirm that the detailed description of each type is shown
    4. Validate correct use of Query Params and display relevant response information to the user (description, duration, use_policy, additionals if applicable, images, etc.)
  3. Step 3: Availability (/Availability)
    1. Verify availability and pricing for specific dates
    2. Validate correct use of Query Params and display relevant response information to the user (from, to, distribution, cancellation_policy, conditions, etc.)
    3. Confirm that the required choice_id for the booking flow is obtained

BOOKING FLOW

  1. Prebook
    1. Correct implementation of the choice_id obtained in the previous step
    2. Validation using exchange_policies (important to pass this response to the client)
    3. Validation using hints
    4. Payment error handling and corresponding error codes
  2. Payment
    1. Correct implementation of the prebook_id obtained in the previous step
    2. Implemented payment methods (specify which ones will be used)
    3. Payment error handling and corresponding error codes
  3. Book
    1. Correct implementation of the prebook_id obtained in previous steps
    2. Payment error handling and corresponding error codes
    3. Voucher/confirmation must display:
    4. Booking date (+ activity entry date)
    5. HotelDO confirmation number
    6. PNR
    7. Ticket/activity details (description + relevant conditions)
    8. Passenger names and quantities
    9. Usage dates (validity dates if applicable)
    10. Cancellation policies (showing dates)
    11. Fees/extras payable at destination if applicable
    12. Important notices (Use Conditions, Terms and Conditions, etc.)

POST SALE SERVICES

Services available 60 seconds after confirmation:

  • Status
  • Will you use your own voucher or HotelDO’s? You can download the voucher and include it in the certification. All voucher information must be passed to the end customer.
  • Cancellations: Manual and automatic. Note that a cancellation applies to all participants; individual cancellations are not allowed.

C - Other Validatons

Ticket Information

  • Ticket/activity name displayed correctly
  • Detailed description of the activity/ticket
  • Clearly visible usage conditions
  • Age restrictions if applicable
  • Activity duration and validity dates if specified
  • Location/address
  • Passenger quantity

Passenger Management

  • Age verification for minors (0–17 years old)
  • Correct categorization:
    • Adults (10+ years old)
    • Children (3–9 years old)
    • Infants (0–23 months)
  • Support for special characters in names (ISO-8859-1)

Error Management

  • Clear mapping between error codes and HotelDO ID
  • Descriptive error messages on your platform

Pricing Information

  • Price breakdown
  • Additional fees if applicable
  • Destination charges clearly identified if applicable
  • Visible and detailed cancellation policies
  • Explanation of cancellation policy calculation

Content

  • Specify whether you use HotelDO static content and how it is consumed
  • Activity/ticket images
  • Activity features

Updated 29 days ago