Skip to main content

Widget Redesign: API and Widget parameter updates

This guide combines all redesign updates and widget customization options into a single reference for API integrations and widget configuration.

With the upcoming widget redesign release, Triparound is introducing improvements to product presentation, category structure and widget flexibility.

Most redesign changes are backward-compatible, and legacy fields will continue to function during the transition period.


1. /activities Endpoint Changes

We have enhanced how products display highlights, itineraries, inclusions and exclusions.

New list fields

The following array-based fields are now available:

Field

Type

Description

highlights_list

Array of strings

Product highlights

inclusions_list

Array of strings

Included items/services

itinerary_list

Array of strings

Day-by-day or step-by-step itinerary

exclusions_list

Array of strings

Excluded items/services (new field)

These fields replace the previous plain-text fields for improved formatting and flexibility.

Legacy fields

The following legacy text fields remain available for backward compatibility:

  • highlights

  • inclusions

  • itinerary

Migration behavior

  • Existing legacy content will automatically migrate into the new list fields.

  • No manual migration work is required.

  • After release, all new and updated activities will only update the new list fields.

Recommended action

We strongly recommend updating your API integrations to use the new list fields as soon as possible, since future product updates will no longer modify the legacy text fields.


2. Categories (/activity-groups Endpoint)

Activity groups are being simplified into a flat structure.

What’s changing

Previously, activity groups could contain nested child groups through the children field.

This structure is now deprecated.

New structure

All activities from child groups are moved directly into the parent group's activity_list.

Example:

  • Parent group with 3 child groups

  • Each child contains 20 unique activities

  • Parent activity_list now contains 60 activities

Important notes

  • children still exists temporarily for backward compatibility.

  • New activity groups will no longer contain child groups.

  • Future implementations should ignore the children field entirely.

Recommended action

Update your integrations to rely on activity_list instead of children.

Please test category handling after release.


3. New Widget URL Parameters

The redesigned widget introduces additional flexibility for standalone mode and multi-product widgets. All existing widgets remain functional.

  • standalone

    Default: false

Enables full-screen widget mode and removes the close (X) button.

Recommended for:

  • External URLs

  • Shared booking links

  • Standalone landing pages

Example

?standalone=true

Recommended action

We recommend adding standalone=true to all external widget URLs before release to ensure the best guest experience.


activity_id

Now supports multiple IDs.

Example

?activity_id=123,456

Creates a multi-product widget showing all selected activities.

No action required.


  • category_id

Now supports multiple IDs.

Example

?category_id=1,2

Displays products from all specified categories.

No action required.


4. Products & Transfers Tabs

The redesigned widget introduces two separate tabs:

  • Things to Do

  • Transfers

These controls only affect multi-product widgets.

Parameter

Default

Description

show_products

true

Shows “Things to Do” tab

show_transfers

true

Shows “Transfers” tab

Recommended configurations

Set to false to hide the respective tabs.

  • Product-only widgets

    ?show_transfers=false
  • Transfer-only widgets

    ?show_products=false

Without these settings, empty tabs may appear and confuse guests.

Recommended action

Update existing multi-product widget URLs before release.


5. Additional Widget Customization Parameters

Other widget URL parameters to define the booking button text and background color and the product information language.

  • Booking button text

    Customize the booking button label directly in the widget code.

    Example

    </> HTML

    BOOK NOW


  • Booking button background color

    Customize the booking button background color through the existing style attribute.

    Example

    background-color:#97843e;


  • Product information language

    Define the language of product content.

    Example

    </> HTML
    data-lang="en"

or

?locale=en


Recommended next steps

Before Release

Update existing widget URLs:

  • Add standalone=true where appropriate

  • Add show_transfers=false for product-only widgets

  • Add show_products=false for transfer-only widgets

After Release

  • Test all widget implementations

  • Update API integrations to use the new list fields

  • Transition away from deprecated category children handling

For questions or support, contact support@triparound.com or consult the API documentation.


See also:

Did this answer your question?