Requirements API v2.8.0

🙅‍♂️ Removing attributes in the /v2/trips response

We have taken the feedback from all of you and improved the readability and developer experience for the API response of the v2/trips endpoint.

The following attributes from the v2/trips API response have been removed.

Example response with highlight of deprecated attributesExample response with highlight of deprecated attributes

Example response with highlight of deprecated attributes

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

entryRestrictions

DESTINATION_TRAVEL_RESTRICTIONS

exitRestrictions

ORIGIN_TRAVEL_RESTRICTIONS

travelRestrictions

ORIGIN_TRAVEL_RESTRICTIONS +
DESTINATION_TRAVEL_RESTRICTIONS

transitRestrictions

DESTINATION_TRAVEL_RESTRICTIONS

documents

ORIGIN_DOCUMENTS +
DESTINATION_DOCUMENTS

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

TRAVEL_RESTRICTIONS

DESTINATION_TRAVEL_RESTRICTIONS +
ORIGIN_TRAVEL_RESTRICTIONS

ENTRY_RESTRICTIONS

DESTINATION_TRAVEL_RESTRICTIONS

EXIT_RESTRICTIONS

ORIGIN_TRAVEL_RESTRICTIONS

DOC_REQUIRED

ORIGIN_DOCUMENTS +
DESTINATION_DOCUMENTS

COVID_19_TEST

DESTINATION_TRAVEL_RESTRICTIONS +
ORIGIN_TRAVEL_RESTRICTIONS

QUARANTINE

DESTINATION_TRAVEL_RESTRICTIONS +
ORIGIN_TRAVEL_RESTRICTIONS

TRANSIT_RESTRICTIONS

DESTINATION_TRAVEL_RESTRICTIONS +
ORIGIN_TRAVEL_RESTRICTIONS

🙅‍♂️ Removing attributes in restrictions, procedures, countries and regions

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

lastCheckedAt

RESTRICTON, PROCEDURE, COUNTRY, REGION

stillCurrentAt

RESTRICTON, PROCEDURE, COUNTRY, REGION

visaStatus

COUNTRY

entryStatus

COUNTRY

exitStatus

COUNTRY

directionality

RESTRICTON, PROCEDURE

durationInDays

PROCEDURE

durationReductionMeasures

PROCEDURE

durationExtensionMeasures

PROCEDURE

enforcementConditions

PROCEDURE

alternativeMeasures

PROCEDURE

📘

Attribute defaultDurationInDays will remain

Based on the feedback we've received we've decided to keep the attribute defaultDurationInDays.

🧭 Category Changes

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)

Improved error messages for unsupported trip segments

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 ->