We have taken the feedback from all of you and improved the readability and developer experience for the API response of the
The following attributes from the
v2/trips API response have been removed.
We've introduced "groupings" as part of the summary that collects and "groups" related travel rules.
Below table illustrates how to map the previously existing attributes to the grouping types.
|Removed attribute||Grouping type to use instead|
In addition we have greatly reduced the number of groupings to focus only on the most relevant pieces of information.
Below table illustrates the grouping types that have been removed and how they map to remaining groupings.
|Grouping type removed||Grouping type to use|
We have received a lot of feedback relating the various attributes and structured information we provide through our API. As the world is changing and adapting, we've identified several attributes that are no longer as helpful as we intended them to be and decided to remove them from our data set. This change greatly improves the readability of the API responses and allows for easier implementations for clients.
Below table illustrates the attributes removed for each entity type in our API.
|Removed attribute||Entity Type|
Based on the feedback we've received we've decided to keep the attribute
To further improve the developer experience and greatly reduce the complexity of travel rules we've consolidated the categorization of restrictions and procedures.
Please see our previous changelog on Procedure Category Changes (Revised)
We are covering more cases for itineraries we currently don't support and are now providing a helpful message that can be displayed to the traveller.
Please read more in our official guide for trips ->