izi travel logo

Izi Logo royalty-free images

5,425,305 izi logo stock photos, vectors, and illustrations are available royalty-free for download..

Our company

Press/Media

Investor relations

Shutterstock Blog

Popular searches

Stock Photos and Videos

Stock photos

Stock videos

Stock vectors

Editorial images

Featured photo collections

Sell your content

Affiliate/Reseller

International reseller

Live assignments

Rights and clearance

Website Terms of Use

Terms of Service

Privacy policy

Modern Slavery Statement

Cookie Preferences

Shutterstock.AI

AI style types

Shutterstock mobile app

Android app

© 2003-2024 Shutterstock, Inc.

izi.TRAVEL - Beta

About this app

Data safety.

App support

More by informap technology center.

Similar apps

The Future of Travel is Now: World Trip Deal Reveals Its AI-Powered Journey Planning

The Future of Travel is Now: World Trip Deal Reveals Its AI-Powered Journey Planning.

Dubai, UAE - April 19, 2024 —

Travel booking has long been a challenging task for adventurers worldwide. The process of filtering through countless flights, accommodations, and activities can be daunting, compounded by user-unfriendly interfaces and strict budget limits.

However, World Trip Deal (WTD), an innovative online travel agency (OTA), proposes a solution to transform the travel booking experience.

World Trip Deal (WTD), led by CEO Mahdi Nourian, utilizes AI to democratize luxury travel, making it affordable without compromising quality.

The company provides personalized itineraries and unique experiences for budget-conscious travelers, revolutionizing the travel industry.

AI Meets Affordability: World Trip Deal CEO on Democratizing Luxury Travel

This approach not only democratizes luxury travel but also enriches journeys, making exclusive experiences accessible to a broader audience.

Many online travel agencies focus on finding the cheapest deals. How is WTD using AI to create a more personalized and luxurious travel experience? (Focuses on personalization and luxury aspect)

World Trip Deal (WTD) redefines travel booking by using AI to curate personalized, luxurious experiences within a reasonable budget.

Unlike typical agencies focusing on generic options, WTD crafts unique itineraries based on individual preferences and history.

This approach offers exclusive deals and luxury experiences tailored to each traveler, ensuring a distinct and memorable journey without financial strain.

With the rise of AI in travel booking, how is World Trip Deal differentiating itself from the competition? (Focuses on competition and differentiation)

Mahdi Nourian: Look, there's no denying it – AI is taking the travel booking world by storm. Competition is fierce, and everyone's scrambling to integrate this powerful technology. 

But here at World Trip Deal (WTD), we're not just following the pack; we're leading the charge. Here's how we differentiate ourselves:

1. Beyond Basic Recommendations:  Many travel platforms use AI to suggest popular destinations or amazing hotel options . WTD goes a step further. We leverage AI to create a unique profile for each traveler. Imagine a travel agent who analyzes your past trips, interests, and budget to curate an itinerary that feels like it was designed specifically for you. No more cookie-cutter experiences!

2. Luxury on a Budget:  Let's face it, affordability is a major concern for many travelers. However, luxury shouldn't be reserved for the high rollers. WTD's AI technology negotiates exclusive travel deals with travel partners, unlocking hidden gems and securing discounts on luxury hotels and unique experiences.

3. Flexibility for the Adventurous Soul:  Travel plans can change, and WTD's AI is built to adapt. Unlike some competitors with rigid AI recommendations, our platform allows travelers to modify their itineraries on the fly . 

4. A Seamless User Experience:  AI shouldn't feel like a black box. WTD's user-friendly platform integrates seamlessly with our AI engine. 

Travelers can search, compare, and book flights, accommodations, and activities all within a single platform. 

No more juggling multiple websites and struggling with complex interfaces. We believe travel planning should be enjoyable, not a chore.

5. Future-Proofing Travel Booking:  AI is constantly evolving, and at WTD, we're committed to staying at the forefront of this technology. 

So, sure, the travel booking landscape is brimming with AI, but at WTD, we offer a distinctly personalized and budget-conscious approach to luxury travel . We're not just suggesting destinations; we're crafting unforgettable adventures tailored to your unique desires.

What role do you see AI playing in the future of travel booking, and how is World Trip Deal preparing for it? (Focuses on future trends and WTD's position)

World Trip Deal (WTD) leverages AI to shape the future of travel booking, promising a dynamic, personalized experience.

Envision AI tailoring itineraries based on real-time factors like weather or mood, simplifying processes such as airport check-ins, and offering real-time translation.

WTD invests in continuous AI advancement, ensuring a seamless, intuitive user experience, and revolutionizing travel from planning to discovery.

●      Transparency with AI: "How transparent is World Trip Deal with travellers regarding how AI is used in the booking process? Do they have any control over the AI recommendations?"

Mahdi Nourian emphasizes transparency at World Trip Deal (WTD), clearly outlining AI’s role in the booking process:

1. Clear Communication: WTD provides easy-to-understand explanations where AI impacts recommendations.

2. AI Preferences: Travelers can tailor their AI interactions by setting preferences for travel style, interests, and pace.

3. Curated Transparency: Instead of complex technical details, WTD highlights when recommendations are AI-driven, based on travel trends and user behaviors.

4. Control Through Customization: The platform allows extensive customization, enabling travelers to refine searches and adjust itineraries.

5. Human Expertise: AI is enhanced by human experts who provide insights to balance and personalize the travel experience.

WTD’s approach ensures that travelers understand and control AI’s input, enhancing their booking experience while keeping personal choice paramount.

Future of Travel and WTD:

●      AI and Sustainability: "Is there a role for AI in promoting sustainable travel practices within World Trip Deal's platform?" 

Mahdi Nourian: at World Trip Deal we emphasize AI’s role in sustainable travel with eco-friendly suggestions and carbon offset options. WTD prioritizes user experience, innovates continuously, and ensures data transparency.

This approach not only enhances travel but also promotes responsible tourism and builds user trust in AI integration.

Finally, let's explore the broader impact of AI on the travel industry.

Transforming Travel:

●      Hyper-Personalization: AI will personalize travel experiences beyond imagination. Imagine itineraries tailored not just to destinations but to your mood, preferences, and even real-time data. AI will transform travel from a one-size-fits-all experience to a truly personal journey.

●      Streamlined Booking & Management: Travel booking will become effortless. Imagine AI automating tedious tasks like visa applications, travel insurance, and even managing itinerary changes with ease.

●      Accessibility & Inclusivity: AI can break down language barriers and assist travelers with disabilities. Imagine real-time translation tools and AI-powered accessibility recommendations, making travel a more inclusive experience for everyone.

However, AI also comes with challenges:

●      Ethical Considerations: Transparency and data privacy are crucial. AI algorithms need to be free from bias and ensure responsible data usage.

●      Human Interaction: Travel advisors still have a vital role. AI shouldn't replace the human touch. We envision a future where AI complements human expertise, offering a dynamic and personalized travel experience.

So, there you have it. World Trip Deal (WTD) is shaking things up in the travel industry with a potent blend of AI and affordability.

From personalized itineraries to hidden gem recommendations, WTD is making luxury travel accessible for the budget-conscious adventurer.

But WTD's vision extends beyond booking. They're looking to leverage AI throughout your entire journey, offering real-time recommendations, fostering a travel community, and even promoting sustainable practices.

 As AI continues to reshape the travel landscape, WTD is poised to be a leader in this exciting transformation.

So, the next time you're dreaming of an escape, ditch the outdated guidebooks and endless price comparisons.

Head over to World Trip Deal and let AI craft the perfect adventure for you. After all, travel should be an unforgettable experience, not a logistical nightmare. And with WTD, it can be just that.

Contact Info: Name: Mehdi Nourian Email: Send Email Organization: World Trip Deal Address: UAE, Dubai, Barsha Heights, Sheikha Noora Building, Office 709 Website: https://www.worldtripdeal.com/

Release ID: 89127569

If you come across any problems, discrepancies, or concerns related to the content contained within this press release that necessitate action or if a press release requires takedown, we strongly encourage you to reach out without delay by contacting [email protected]. Our committed team will be readily accessible round-the-clock to address your concerns within 8 hours and take appropriate actions to rectify identified issues or support with press release removals. Ensuring accurate and reliable information remains our unwavering commitment.

Logo-Izi-Travel-1-300×300

Leave a Comment Cancel Reply

Save my name, email, and website in this browser for the next time I comment.

Check here to Subscribe to notifications for new posts

Privacy Overview

• Documentation Powered by Slate

This is the API reference document for accessing the izi.TRAVEL Directory (MTG Content Directory):

• izi.TRAVEL API notes
• License Terms of the izi.TRAVEL API
• izi.TRAVEL Academy

All API requests are made over HTTPS to API endpoints.

The response format for all requests is a JSON object or array of objects.

Data character encoding is UTF-8.

Whether a request succeeded is indicated by the HTTP status code. A 2xx status code indicates success, whereas a 4xx status code indicates failure. When a request fails, the response body is still JSON, but always contains the fields code and error which you can inspect to use for debugging.

API declares Generic Errors codes, applicable for all requests. However, an endpoint can declare own error codes.

High-Level Models

Museum Tours

Starting from API version 1.2.3 , the “Museum Tours” feature is introduced extending the concept of navigational story to Museum’s collections for showing the visitor “navigational pictures/audio” between exhibits and allowing the visitor to understand where to go next. More than one navigational stories are allowed between two exhibits.

The order of exhibits and story_navigations in collections is important for the feature and the order is defined in izi.TRAVEL CMS (Content Management System). Corespondent API end-points will return collection’s children in this order.

Highlights:

• If indicated API version is 1.2.3 or above, in Full form of MTGObject for collection :

– story_navigations will be returned (if exist) in section children in additional to exhibits and in the order defined in izi.TRAVEL CMS.

– Playback object will be returned with type as sequential and order as arrays of ordered exhibits and story_navigations UUIDs.

children_count field for collection will always return the number of exhibits , it does not depend on indicated API version (See Compact form of MTGObject and Content of MTGObject Full form). To get the number of exhibits and story_navigations in a collection use /mtgobjects/:uuid/children/count end-point (see next bullet).

/mtgobjects/:uuid/children/count end-point will return the number of exhibits and story_navigations in a collection if indicated API version 1.2.3 or above.

/mtgobjects/:uuid/children end-point will return exhibits and story_navigations for a collection in the order defined in izi.TRAVEL CMS.

audio_duration and size fields will include story_navigation data for collections and museums if indicated API version is 1.2.3 or above (see MTGObject Compact and Full forms).

playback section of quest example:

Starting from API version 1.3 , new playback type quest is introduced in additional to random for gamification of audio guides.

The idea is in dividing guide into segments, where first segment is always visible to the end-user at quest start, next segments (quest parts) will be opened after completion of certain conditions.

First quests will be based on tour and available in 15Q4. Each tour segment consists of one or more tourist attractions and navigational points. Each tourist attraction and navigational point belongs to one segment. Any segment might be visible to the end-user if quiz in specific tourist attraction is answered or specific TA has been “visited”, meaning its trigger zone has been entered to. Such tourist attractions called Open Segment control points, another type of control points is End Quest indicates completion of the quest.

A quest tour consists fifteen tourist attractions ( TA1 - TA16 ) and one navigational story ( SN13 ). The tour has 5 segments, where Segment 1 is visible to the end-user on device and it has control point TA3 with quiz. If the end-user reached TA3 and correctly answered the quiz, Segment 2 will be opened (made visible to the end-user), otherwise, Segment 3 will be opened. TA8 makes similar quest branching for opening Segment 4 and Segment 5 respectively. Segment 4 can be opened if the end-user goes via Segment 2 and reached one of TA5 trigger zones.

TA11 and TA15 are End Quest control points and after correct answer on TA15 quiz or reaching TA11 , the quest is marked as completed.

On End Quest , the client shall show closing_line - to congratulate the end-user with successful end of quest, see section Content . The closing_line is optional and the client shall form own congratulation message if the closing_line is not provided. The closing_line can keep URLs to quest author pages.

Other behavior of End Quest , like any quest points gathering and results sharing in social networks, are parts of clients.

At the right of the screen you can see JSON of playback of the quest example. Important note : the playback schema does not declare control points in a segment to open other segments, but supposes declaration of conditions in a segment that open this segment. Following the example, Segment 4 declares opening conditions: TA8 correct quiz answer or TA5 trigger zone. Rationale : further opening conditions can not be linked to control points from other segments, for example, depending on time/date, arbitrary trigger zone, scanning of QR code, etc

For more details see: Playback , Segment , Conditions , Quiz

To have early knowledge of playback type, playback_type field is returned in root of museum , collection and tour objects. See MTGObject Full , Compact forms. playback_type field either is returned for museum and tour in /featured/mobile end-point.

Objects with playback type quest for old API versions will not be returned: if API version indicated in requests is below 1.3 , correspondent endpoints will return HTTP 404 ‘Not Found’ for quests or quests will not be included in responses, for example, in search or publisher end-points.

Authentication

All API requests require an API key to be included into request:

Make sure to replace 14010cf2-3151-475d-a7ae-234ba057424f with your API key.

All API requests require an API key. The API key shall be included in a header that looks like the following:

X-IZI-API-KEY: 14010cf2-3151-475d-a7ae-234ba057424f

For debugging purpose there is an option to pass an API key via a parameter api_key . Please note: if password passed via header and via parameter at the same time, the password from header will be used in the request.

An API request should include API version number.

There are two ways to request a specific version:

• Send as a query parameter version .
• Send version in the HTTPS “Accept” header: application/izi-api-v[VERSION]+json
• If the API version passed via parameter &version= , the version will be used in request,
• Otherwise, the version from ‘Accept’ header will be used (if indicated),
• Otherwise, the most early supported version will be used - currently it is 1.2 .

Supported versions: 1.2 , 1.2.1 , 1.2.2 , 1.2.3 , 1.2.4 , 1.2.5 , 1.3 , 1.4 , 1.5 , 1.6 , 1.7 , 1.8

Limited content access

By default, only public available content can be retrieved using the API. The state of the content is marked as published in status field of API responses.

For debugging purposes, a content can be marked as limited in izi.TRAVEL Content Management System (CMS). In this case, a mobile application can get access to limited content specifying an access password (In terms of izi.TRAVEL CMS it is called passcode ).

There are two ways to pass an access password in an API request:

• Send in a header X-IZI-API-PASSWORD .
• Send as a query parameter password .
• If the password passed via header, the password will be used in request,
• Otherwise, the parameter value will be used,
• Otherwise, only published content will be filtered.

Generic Errors

The izi.TRAVEL API generic error codes:

Most of API requests require &languages= parameter. The parameter defines one language or list of languages as a filter to retrieve content that has localization on that or those languages.

An API client usually passes it as a list of the end-user preferable languages, for example, browser or device locale, manually set by the end-user in applications settings, etc. The order of languages makes sense, when the list of languages will be processed from left to right.

Example 1: &languages=ru,en,nl,de

izi.TRAVEL system will try to return content for first language ru , taking into account all other filters in API request. If content localized on ru does not exist or does not match other filters, the system will try to return content on en language and so on – next nl and last de . If there are no matches for all indicated languages, API will return 404 “Not Found” or empty array.

Example 2: &languages=any

Starting from API version 1.2.4 , a special keyword any can be used in &languages= parameter. The any keyword sets a filter for languages used in izi.TRAVEL Directory: only languages used in existing content and the list can be retrieved via /languages/used end-point. In other words, the any keyword will be replaced by the list returned by /languages/used . Please note, the used languages list is specifically ordered. Please note, if any keyword will be indicated with API version below 1.2.4 : HTTP 404 ‘Not found’ will be returned or empty response.

Example 3: &languages=de,nl,any,ca

The any keyword can be used with direct indication of languages. In this example, the system will try to return content for de and next for nl languages. If no content has been matched for de and nl , the used languages list will be used (excluding already processed de and nl , if such exist in /languages/used ). Anything to the right of the any keyword will be ignored - ca will be omitted from the languages filter in the example.

Example 4: &languages=de,vv,,nl,any

Any not supported languages (including empty/blank) will be ignored, for example, vv will be excepted from filter as not included in supported by izi.TRAVEL languages - the list of supported languages (where content is already exists or can be created in izi.TRAVEL Directory) can be obtained using /languages/supported end-point.

This section provides some notes about parameters passing to API.

If a parameter is indicated several times in URL, only latest will be taken into account, for example, if passed &type=city&type=museum&type=tour only latest parameter &type=tour will be used and API will filter only tours.

An array parameter should be passed as a key and comma separated values, for example, &languages=fr,it,en

Another not recommended form of an array parameter is the following &some_key[]=value_1&some_key[]=value_2&some_key[]=value_3 that equals to &some_key=value_1,value_2,value_3 . Example &except[]=city&except[]=publisher&except[]=country , however, this form increases the length of URL and can cause ‘HTTP 414 Request-URI Too Large error’, you shall use the short form &except=city,publisher,country instead. Please note: in rare cases several values can be passed in one array key, for example, &some_key[]=value_1,value_2&some_key[]=value_3 where first keeps two values and second keeps one value, however, it is not fully supported and SHALL NOT BE USED.

For some array parameters the order of values makes sense, for example, &languages=nl,fr,it see Languages , for other parameters it does not, for example, filtering by type of content &type=city,museum,collection .

In most cases, invalid parameters (including values) are ignored and API does not raise an error returning HTTP 200 'Ok’. In this case the client can get not relevant response or HTTP 404 'No Found’ or empty response. For example, &type=museum1.... there is no museum1 type of object and search end-point will return an empty array.

Some of parameters (including values) depend on passed API version and can be ignored, for example, staring from API version 1.2.4 ( Languages ) a special keyword any can be used in &languages= parameter. If the any keyword will be used for API versions below 1.2.4 (indicated in request), the client will get HTTP 404 'No Found’ or an empty response.

There are special behavior for passing API version and password where parameter or header ways can be used, see Versioning and Limited content access

• Media Access

Media files (images, audio, video, etc.) are stored in media directory and scaled\transcoded to required formats. A media file access link (URL) depends on type of a media and described by one of patterns below. In most cases mobile developer can dynamically build needed media file URL basing on data response parameters.

And supports versions of the more modern Transport Layer Security ( TLS ) rather than SSLv3. The media directory serves HTTPS requests using Server Name Indication ( SNI ), however, not all clients support SNI, in this case, if you can control which browser or device your users use, have them upgrade their browser to one that supports SNI, otherwise, use HTTP instead of HTTPS.

Images (Story)

An example of forming an image URL with size 800x600:

When type of images is story or for_recognition , see Media object

URL pattern:

{MEDIA_BASE_URL}/{CONTENT_PROVIDER_UUID}/{IMAGE_UUID}_{IMAGE_SIZE}.jpg

Parameters:

Example: https://media.izi.travel/15ad4ee2-ff56-4a86-950d-8dee4c79fc35/320175a3-d211-4b42-bd92-1fa60851f824_800x600.jpg

Images (Museum’s map, Publisher’s cover)

An example of forming an image URL to a Museum map:

When type of images is map and brand_cover , see Media object

{MEDIA_BASE_URL}/{CONTENT_PROVIDER_UUID}/{IMAGE_UUID}.jpg

Images (Publisher’s logo)

When type of images is brand_logo , see Media object

{MEDIA_BASE_URL}/{CONTENT_PROVIDER_UUID}/{IMAGE_UUID}.png

Images (Sponsor Logo)

When type of images is sponsor_logo , see Media object and Sponsors

Audio (Story)

An example of forming an URL to audio:

When media is audio and type of media is story , see Media object

{MEDIA_BASE_URL}/{CONTENT_PROVIDER_UUID}/{AUDIO_UUID}.m4a

Video (Story)

An example of forming an URL to video:

{MEDIA_BASE_URL}/{CONTENT_PROVIDER_UUID}/{VIDEO_UUID}.mp4

Image (City)

An example of forming an URL to ‘Amsterdam’ City image:

Image for City: Media in City’s Compact and Full forms.

{MEDIA_BASE_URL}/cities/{CITY_UUID}/{CITY_IMAGE_UUID}.jpg

HTTP Compression

gzip HTTP compression example:

It’s recommended to use HTTP(S) Compression for faster downloads, where gzip compression scheme can be used. To switch on the compression, you shall indicate gzip in Accept-Encoding header field of HTTP(S) requests, for example, add Accept-Encoding: gzip into request headers. The server will add a Content-Encoding: gzip header field in the HTTP(S) response returning gzip compressed data.

To improve transfer speed, a API client can use Includes/Except feature to receivie only the portion of the data that a client is interested in.

Content Caching

The izi.TRAVEL API provides an ability to support caching of data. Advanced clients (applications) use content caching to decrease network cost and improve responsiveness for the end-user.

Most of objects in izi.TRAVEL API have field ‘hash’ for the cache control . It is 40 chars string that reflects changes and shall be used for validating client’s caches.

For example, a client loaded a tour with children including media into an internal cache. Next time, when an user lists tours or open the tour, the client can check the hash of the tour in responses (like compact form) and validate the cache.

If a tourist attraction of the tour was changed (for example, description updated or new image added), the hashes of the tourist attraction and the tour are changed. Another case, a new tourist attraction is added to the tour and tour’s hash will be changed as well.

If the client defines such changes, it marks the tour as expired and shall reload JSON of it to define what content shall be updated, added or deleted. In this example, it will reload objects of the tour and the tourist attraction, load new image of the tourist attraction, load new tourist attraction … when other objects and its loaded media can be used from the cache.

The attached PDF reflects most importent cases when hashes are changed hashes_changes.pdf

Includes/Except

Example: Get a tour excluding most of sections (make the request with and without except parameter example):

The API provides an ability to indicate certain sections to be included into returned objects using parameters includes and except in endpoints . It allows to improve performance of API calls (in additional to HTTP Compression ) by receiving only the portion of the data that a client is interested in. The following table reflects sections names (the parameters values) that can be used for partial response.

There are two special words all and none can be used in the parameter includes .

A request with &includes=all will return everything in responses (above mentioned sections) and an API client can indicate not required sections via except parameter in the request in order to reduce response size. For example, &except=city,country,publisher , &except=children,download,location .

If the value none is indicated in includes parameter, only publisher , location , city_images , route and reviews will be included into response, when other from the table will be excluded.

MTGObject - Compact form

Mtgobject - full form, city compact form in mtgobjects, country compact form in mtgobjects, user generated data.

API does not examine and does not transform most of user generated data (text data entered by content providers in izi.TRAVEL Content Management System) and returns data as is.

API Clients SHALL PROTECT own product from XSS attacks and make correspondent actions, like HTML Sanitization .

The documentation marks corresponding fields as Note: User Generated Data across whole document.

izi.TRAVEL API provides data as MTGObject.

MTGObject (Mobile Traveler Guide Object) is a core content object used by mobile developers. MTGObject, depending on its type property, represents any MTG Content object (museum, exhibit, collection, tour, tourist_attraction, story_navigation).

An MTGObject can be requested in full or compact forms (formats).

There is another set of objects, like Country, City, Publisher, Content Provider, etc that assists MTGObjects.

• MTGObject Full Form

Museum MTGObject Full form example (wo children):

Full MTGObject is used to display details of particular content object: exhibit, tour, museum, collection, navigational story, tourist attraction.

See examples:

• Get a tourist attraction example
• Get a museum without children example

Get a museum with certain objects (sections) in response

Get a tour with certain objects (sections) in response.

• MTGObject Compact Form

Museum MTGObject Compact form example:

Compact MTGObjects are used to display a list of items.

• Find museum by name example
• See children section in Get a tour with certain objects (sections) in response
• Get Publisher’s Museums and Tours eample

Publisher Full Form

Publisher Full form example (without children):

Full form of Publisher object.

Publisher Content

Publisher contacts.

Name: contacts

Publisher Compact Form

“publisher” section example in MTGObject(museum, tour, etc):

“publisher” compact form:

Compact form of Publisher object. Name of section in common MTGObjects is publisher .

City Full Form

City Full form example:

Full form of City example with images and translations:

Full form of City object.

City Content

City compact form.

“city” section example in MTGObject(museum, tour):

“city” object example with images and translations:

Compact form of City object. Name of section in common MTGObjects is city .

• Find “Baltimor” City example
• Get City endpoint
• Get list of Cities endpoint
• Get Country’s Cities endpoint

Country Full Form

Country Full form example:

Full form of Country example with translations:

Full form of Country object.

Country Content

Country compact form.

“country” section example in MTGObject(museum, tour):

“country” object example with translations:

Compact form of Country object. Name of section in common MTGObjects is country .

City/Country Translations

“translations” section example:

Translations section of City/Country.

• Examples in Get City endpoint

“contacts” section example:

Name: contacts .

Museum’s contacts.

“content” section example:

Name: content .

• Content Provider

“content_provider” section example:

Name: content_provider .

Provides Content Provider information.

“download” section example:

Name: download .

This object contains map-mbtiles - a file with geo off-line map in mbtiles format for current MTGObject (museum, tour, quest).

Museum’s “location” section example:

Exhibit’s “location” section example:

Name: location .

Geo and indoor positioning.

“map” section example:

Name: map .

Mapping details.

“audio”, “images” section in an object (museum, tour, exhibit,…) example:

“images” section in Publisher object example:

A) Objects names: images , video , audio

auidio and video are applicable for museum , tour , tourist_attraction , exhibit , collection

video with type youtube is described below in section C).

B) Objects names: images for City and Publisher cover

C) Object name video with type youtube . Available form API version 1.2.5 or above, see Versioning :

“playback” section for type “sequential” example:

“playback” section for type “quest” example:

Name: playback .

MTGObject’s playback algorithm describes how to play data inside MTGObject and its children.

Typical for tour , museum and collection objects.

Values: random , sequential or quest .

sequential – a consumer must follow a sequence of children MTGObjects one by one. Order is defined by order parameter, if set, a mobile application can use this data for making decisions which story to play. The first array element is the starting object to play. See “Museum Tours” ), the section will include ordered exhibits and story_navigations UUIDs for collection and the order is important.

random – the same, as above, but order is not important. Typical for museum and tour objects.

quest - is a segmented object (see Quests ), where a segment is set of assigned children (for example, tourist attractions) where a child is assigned to one segment only. First segment is always opened at start (available for the end-user). Other segments are opened on client side by quests conditions Open Segment when End Quest conditions indicate completion of the quest (see Segment ). The playback type is defined in segments parameter. quest type is introduced in API version 1.3 . Typical for tour objects.

• tour content can have random or quest playback types.
• museum content can have random and other types in future content.
• collection content can have sequential type (see “Museum Tours” ) and other types in future content.
• playback_type field is returned for museum , collection and tour objects for API version 1.3 or above. See MTGObject Full , Compact forms.
• Quests overview
• JSON schema
• Example Get a tour with certain objects (sections) in response

“purchase” section example:

Name: purchase .

Commercial content purchase details.

“schedule” section example:

Name: schedule .

“quiz” section example:

Name: quiz .

There are two types of quizzes: multiple-choice question and open-ended question .

multiple-choice question is a form of quiz when the end-user is asked to select one answer from an answers list where one answer is marked as correct.

open-ended question is a form of quiz when the end-user is asked to enter answer and API client checks correctness form the list of possible answers. This type is introduced in API version 1.3 (see Versioning )

quiz answer

See Get a tourist attraction example

Trigger Zone

polygon “trigger_zone” section example:

circle “trigger_zone” section example:

Name: trigger_zone .

Place where media content must be played.

izi.TRAVEL allows to rate content like museum , collection , exhibit , tour and tourist_attraction , lets leave a review on the content and retrieve ratings/reviews for certain content and language. See Rating & Reviews endpoint .

izi.TRAVEL periodically calculates the average of ratings/reviews per content and provides it in optional section reviews of MTGObjects ( Compact , Full forms) and in metadata section of Rating & Reviews endpoint responses.

Reviews section example:

• A rating/review is made for certain language version of content and can include only rate , only review or the pair (see POST method of Rating & Reviews endpoint ). The rate value is [0..10], where O means not rated.
• The average is made across all languages of a content.
• The total number of ratings in the average reflects only count of ratings/reviews where rate was set ([1..10]).
• The total number of reviews in the average reflects only count of ratings/reviews where review was left.
• The average of a museum includes average of the museum (if exists) and averages of its collections if the collections’ averages exist.

5-Stars Rating

izi.TRAVEL clients use 5-Stars Rating and shall calculate value as “((Float)((floor(rating_average + 0.5)) / 2.0))”

izi.TRAVEL allows to reflect sponsors of content. Since API version 1.2.2 . The section sponsors will be returned in MTGObject Full Form , if at least one sponsor object exists, sponsors included (see Includes/Except ), and indicated API version is 1.2.2 or above (see Versioning ).

Sponsors section example:

“quest” playback example:

Name: segment .

An audio guide can be segmented, for example, quest (see Quests overview), where a segment object represents a part of a guide as a set of guide children belong to the segment. A guide can define different ways of guide passing using segmented approach. The definition is represented in Playback algorithm. The guide branching based on certain conditions. For example, in quest guide, next segment will be visible to the end-user on correct answer of a quiz , another segment will be visible on incorrect answer of the quiz or on entering to a trigger zone .

In first releases there are two conditions : quiz and trigger zone of objects, however, in future other types can be added, e.g. depending on time/date, arbitrary trigger zone, audio playing completion, scanning of QR code, etc.

The system usually returns an object and its children depending on requested language and publications states, for example, for a tour T1 on en language request, an end-point will return tourist attractions TA1, TA2 as they have en language profiles and are in published state, for another request where nl language and pass-code (password) indicated, the end-point will return TA1, TA3, TA4 as only these tourist attractions have nl profiles and are in state published or limited .

Please note, the playback algorithm does not depend on existing languages profiles and publications status and keeps all guide objects, otherwise, the playback algorithm does not make sense. In izi.TRAVEL CMS such guide will be passed via validation mechanism by content author (provider) request, however, clients shall correctly process possible invalid state of playback algorithm, for example, if some quest has a quiz conditional point that opens another segment, but the point does not have quiz for certain language, the client shall notify end-user about inability to play quest as well as push warning to own logging/alert system or proposing to leave a review to be further reported to the content author.

Operator or

Operator and.

“quiz” condition example:

“trigger_zone” condition example:

Conditions are used in playback algorithm, for example, in Quests , see Playback and Segment .

Quiz Condition

Name: quiz_condition

quiz_condition is true for quiz of item if:

• correct_answered is set to true and the end-user correctly answered the quiz;
• correct_answered is set to false and the end-user has not answered the quiz;

otherwise, quiz_condition is false .

Trigger Zone Condition

Name: trigger_zone_condition

trigger_zone_condition is true when the end-user enters to any trigger zones of item .

Search for MTGObjects, Cities and Countries

Find all cities which have content on English language and sort them by name:

Find all tours, cities and countries which have content in English and Dutch and also have ams in their title:

Find all countries which have content in Russian and sort them alphabetically:

Find all tours with English language, do not include publisher section to results Compact MTGObjects, but include city section:

Find all museums and collections with English language for only two Publishers (availble form version 1.2.4):

Search for resources in izi.TRAVEL Directory, based on many filters parameters, supporting full-text and geo- searching, transparent sorting and pagination.

TABLE OF CONTENTS:

Objects filtering by types

Query (Full Text Search)

• Geo Search - Search geo-areas - Geo search type - Current geo distance - Tour’s locations

Free Walking Mode (FWM)

Filtering by rating

Publishers scope

Special Projects

• HTTP REQUEST
• ERROR CODES

FILTERS (SEARCH SCOPE)

By default, the search is applied to museums and tours. To include other objects types and find only certain types, the &type= parameter can be used, indicating one type or several types: museum , tour , city , country , collection , exhibit , tourist_attraction or story_navigation .

Starting from API version 1.6 , tours can be filtered by playback type:

• If &type= parameter is not indicated or it keeps tour value, any tours will be returned.
• If &type= parameter keeps tour_random , only tours with playback type random will be filtered.
• If &type= parameter keeps tour_quest , only tours with playback type quest will be filtered.
• If &type= parameter keeps tour and subtypes ( tour_quest or/and tour_random ), all tours will be returned without a warning.
• If &type= parameter keeps tour_quest and tour_random - all tours will be returned without a warning.

By default, the search is applied to museums and tours . To include other objects types and find only certain types, the &type= parameter can be used, indicating one type or several types: museum , tour , city , country , collection , exhibit , tourist_attraction or story_navigation .

The search API allows to filter content localized for certain languages (see Languages ), as well as limited content (see Limited content access ).

The search API allows to execute a search query and get back search hits that match the query parameter.

query search is applied across three fields of MTGObjects : - title field of MTGObject, see title in Compact Form and in Content of Full Form - desc (description) of MTGObject, see desc in Content of Full Form . A story description can have HTML tags and HTML encoded characters. Starting form July 2106, the end-point strips diacritics and HTML elements from the descriptions replacing HTML entities with their decoded value at search time (not in original descriptions) Example: 1) Original description: <p>Par&iacute;s</p> ; 2) HTML stripped description for search: París 3) Final description for search after diacritics stripping and lowercase: paris . In other words, Paris or París query strings will match content with Paris or París or Par&iacute;s . - city names and country names of the object. The search will be made in all translations of assigned city and country. For example, if there are only published content on en language in Paris city and the end-user typed Parijs , the en content was not returned before July 2016 even the city has translation Parijs on nl language, starting from the July 2016 improvement the end-point will return content en if &query= value matches translations of city/country as well, in this case matches Parijs .

query search is applied on title field of City/Country objects. See title in City Compact Form or in ‘Content’ of Full Form ; in Country Compact Form or in 'Content’ of Full Form . Please note: by default, city and country no included in search. See type parameter in request below. For city objects (starting from July 2016), the search will be made in all translations of assigned country.

query search is applied on fields depending on languages passed in parameter &languages= . In other words, query will be made on localized versions of content (if exist for passed languages).

query search will be done from the beginning of words. For example, if a title is “Amsterdam Museum” , than &query=Amster or &query=Mus will match the title, when &query=terdam or &query=seum will not.

query performs case insensitive search, for example, if a title is “Walters Art of Museum” , the following examples &query=WALTERS , &query=aRT , &query=MuseuM will match the title.

Starting from July 2016, the end-point strips diacritics , Before, if the end-user enters 'París’ with a dicritic – only content exactly matched query string 'París’ was returned, now the end-point will match 'Paris’, 'París’ for 'París’ query string and vice versa - will match 'Paris’, 'París’ for 'Paris’ query string.

If there are several words (tokens) in query parameter, the search will use AND operator for the tokens. For example, if a description is “Beautiful canal houses, world famous museums and bustling market squares.” , the following examples &query=Beautiful canal house , &query=Beautiful Houses and Museums will match the description, when &query=All Beautiful Houses and Museums will not due to “All” token.

Search geo-areas

The end-point provides an ability to search objects in some geo-area, for example, to show nearest attractions for the end-user. The geo-area is indicated by &lat_lon= and &radius= parameters. However, actual search geo-area will be a rectangle (square) that embeds the circle. In additional, the end-point offers excluding some geo-area from a search at the same time, using &ex_lat_lon= and &ex_radius= parameters.

From API version 1.6 , the search geo-area can be set by arbitrary bounding box using parameter &bbox= . The same thing for exclusion geo-area - &ex_bbox= parameter can be used instead of &ex_lat_lon= and &ex_radius= . The format of &bbox= and &ex_bbox= is comma separated coordinates: s,w,n,e (bottom, left, top, right), example: &bbox=59.562249,30.108907,59.564046,30.112454 .

• Inclusion and exclusion do not depend on each other and can be indicated both or alone in a request.
• If &lat_lon= and &radius= are indicated and &bbox= parameter is indicated - '400 Bad Request’ will be returned.
• If &ex_lat_lon= and &ex_radius= are indicated and &ex_bbox=  parameter is indicated - '400 Bad Request’ will be returned.

Example: Search in some geo-area by arbitrary box, excluding geo-area indicated by geo-point and radius - &bbox=52.36,4.7;52.38,4.9&ex_lat_lon=52.3758981,4.898879&ex_radius=200

Please note, in case of &lat_lon= indication, the objects in responses are sorted (last sort, see 'SORTING’ below) by distance from &lat_lon= to object’s location (location of tour’s nearest TA or object’s location for other objects types). If objects do not have location (see also geo_distance ) its will be at the end of the geo-sorted list. When &radius= is used, the &lat_lon= parameter is mandatory, and sorting by Geo-distance is always last made. &lat_lon= is not required for &bbox= parameter and you shall set &lat_lon= to have sorting by Geo-distance (See 'Current geo distance’ and 'SORTING’ below).

Geo search type

By default, the end-point will find objects in some geo-area by interception with map bounds of objects. In API version 1.6 , new parameter &geo_search_type= was added with values map_bounds and location . Note: &geo_search_type=map_bounds can be omitted as it is default behavior for the end-point.

In case of map_bounds search type and indicating requested geo-area (inclusion and/or exclusion):

• city , country , museum will be filtered if their map_bounds intercept requested geo-area;
• collection , exhibit will be filtered if location of their museum is in requested geo-area;
• tourist_attraction will be filtered if their location is in requested geo-area;
• tour will be filtered if one of its published/limited tourist attractions is in requested geo-area.

In case of location search type and indicating requested geo-area (inclusion and/or exclusion):

• city , country , museum will be filtered if their location is in requested geo-area;
• collection , exhibit will be filtered if location of their museum is in requested geo-area (the same behavior as for map_bounds search type);
• tourist_attraction will be filtered if their location is in requested geo-area (the same behavior as for map_bounds search type);
• tour will be filtered if one of its published/limited tourist attractions is in requested geo-area (the same behavior as for map_bounds search type).

Current geo distance

Starting from API version 1.6 , if &includes= parameter will keep geo_distance word and &lat_lon= parameter will be indicated, objects in the response can keep geo_distance numeric field reflecting distance in meters from &lat_lon= geo-point to the object location: it is distance to a nearest published/limited tourist attraction for tours, and, it is distance to Location for other object types. The geo_distance field is optional and objects without geo_distance will be at the end of the geo-sorted list. See p.4 in 'SORTING’ chapter below.

Tour’s locations

Starting from API version 1.6 , if &includes= parameter will keep locations word, the response for a tour can keep locations of all published and limited tourist attractions of the tour in format “lat,lon;lat,lon;...;lat,lon” . Please note, locations in responses is optional field.

Starting from API version 1.6 , there is a filter for Free Walking Mode. If &fwm=true will be indicated in the search end-point, only content available in FWM will be returned:

• city and country objects are always available in FWM.
• museum , tour , tourist_attraction can be available in FWM (depending on FWM options set by content providers in izi.DIRECTORY).
• collection , exhibit , story_navigation are not available in FWM.

Starting from API version 1.4 , rated content ( museum , collection , tour ) can be filtered by rating_average (see Rating & Reviews ) as well as sorting by rating (see below). To filter content by rating, the following parameters rating_min and rating_max shall be used. The value of the parameters is integer from 0 to 10 where 0 is used for not rated yet content. Please note, izi.TRAVEL clients use 5-Stars rating for the end-users (see Rating & Reviews ), so rating_average values 10 , 8 , 5 , 2 are 5 , 4 , 2.5 , 1 in 5-Starts rating respectively.

Notes: - Default value for rating_min is 0 . - Default value for rating_max is 10 . - If rating_min and rating_max values are not integers or not in [0..10], an HTTP Error 400 “Bad Request” will be returned. - If both rating_min and rating_max are indicated, rating_min shall be equal to or less than rating_max , otherwise, an HTTP Error 400 “Bad Request” will be returned.

Examples: - &rating_min=4 filters content that has rating equal to or greater than 4 (from 2 to 5 in 5-Stars ) - &rating_min=10 filters content that has rating equal to or greater than 10 (only 5 in 5-Stars ) - &rating_min=4&rating_max=8 filters content that has rating equal to or greater than 4 and equal to or less than 8 (from 2 to 4 in 5-Stars , note: rating_average , for example, with value 4.25 will not be in the range) - &rating_max=7 filters content that does not rated yet or has rating equal to or less than 7 (from 0 to 3.5 in 5-Stars ) - &rating_max=0 filters content that does not rated yet ( 0 in 5-Stars ) - &rating_min=4&rating_max=4 filters content that has rating equal to 4 only, in other words, only content that has exactly 4.0 in rating_average field, not 4.1 or 3.9 )

From API version 1.2.4 (see Versioning ), an ability to limit existing search by publisher or several publishers has been added.

If clients will pass one or several Publishers’ UUID’s using parameter &publishers= and indicate API version 1.2.4 or above, the end-point /mtg/objects/search will make search of tours/museums (or objects with types indicated in type parameter) for only passed Publisher’s UUID’s, preserving filters, sorting and other parameters, like geo-distance, sorting by title or parameter includes/except.

Exceptions/Comments:

If one of UUIDs in &publishers= has not valid format, 422 error will be returned.

If all of UUIDs in &publishers= do not exist, an empty array will be returned with status 200 Ok.

If some of UUID in &publishers= does not exist, an error will not be raised and this UUID will be ignored in the request.

If &publishers= is indicated, however, type parameter keeps city or country , an error 400 will be returned.

Limit of the number of Publisher’s UUIDs is 50, if exceeds. 413 will be returned.

If &publishers= is empty (blank), the parameter will be ignored as done in other end-points.

• &type=museum,collection&publishers=69eb8c07-ce14-4839-ba3d-f4686ea3c9d2,50b5f15b-7328-4509-8250-d36a523292b3 - makes search of museums and collections for only two Publishers.

Special Project is a promotion content in additional to Editor Choice featured content . Special Projects are used to create an interest to outstanding content or special actions in certain region: tours , quests or museums .

A client could show the special projects in dedicated UI section by filtering only special projects using &filters=special_project parameter and indicating region using geo-search filtering, like certain bounding box ( &bbox= ) or city ( &region=<City UUID> ).

Special Projects have internal positive weight (not provided via API) to order content depending on the promotion value, the weight of non special projects content can be treated as zero. To sort special projects, a client shall add to request &sort_by=special_project parameter (see SORTING section below) that will sort special projects in descending order (most rated/promoted on top).

For special projects, a client shall use summary field of content, see MTGObject Full Form and MTGObject Compact Form . If the summary filed is empty, the client shall use the title field.

Other filters parameters you can find in PARAMETERS table below.

Starting from API version 1.6 a new form called short is introduced in the end-point in additional to compact . The form allows improving performance of API calls by reducing traffic. If &form=short is indicated, the response will include only object’s uuid , type and hash . If a client uses caches, it can show objects from the cache or, in case of missing or outdated object ( hash value), it can retrieve such objects using /mtgobjects/batch/:uuid,:uuid,:uuid end-point.

There are three optional fields can be added to response:

locations - see above Current geo distance in Geo Search section

geo_distance - see above Current geo distance in Geo Search section

location - latitude and longitude of object if &includes= parameter will keep location word, example of section  "location": { "latitude": 52.379097, "longitude": 4.89442} . The location of object is described in Location .

See example Tours: search and return in short form

1) If results keeps City or Country objects in additional to museum, tour, etc, Country objects will be returned first, next City objects and finally rest of objects. Each set will be sorted according to next sorting criteria. 2) If &sort_by=special_project parameter is indicated, content that marked as special projects will be sorted (see Special Projects above in FILTERS (SEARCH SCOPE) section). When special projects have positive weight, the weight of non special projects content can be treated as zero. &sort_by=special_project will sort special projects in descending order (most rated/promoted on top), it’s equivalent to &sort_by=special_project:desc (format of &sort_by= parameter see below). If not only special projects were filtered, not special projects content will be after the sorted special projects. 3) Results will be sorted by relevance - with the most relevant results first, for example, when query search is used. 4) If sort_by parameter(s) is(are) indicated, correspondent sorting will be applied on results. The format of the parameter is the following &sort_by=<type>:<order> , where <type> is by rating , by popularity or by title and optional <order> that defines sort in ascending or in descending orders, values asc or desc . By rating - sorts by rating of tours, museums, collections in descending order (similar to &sort_by=rating:desc) , to return in ascending order indicate &sort_by=rating:asc ; By popularity - sorts by popularity of tours, museums in descending order (similar to &sort_by=popularity:desc) , to return in ascending order indicate &sort_by=popularity:asc ; By title - sorts by localized title of tour, museum in ascending order (similar to &sort_by=title:asc ), to return in descending order indicate &sort_by=title:desc . Important note: if several languages are passed in the request and there are publisher’s tours, museums with several translations intercepted with passed languages, the sorting by title can be broken, in other words, sorting by title will correctly work when one language is passed via &languages= parameter.

One, two or all sort_by types can be indicated, for example, for sorting using all types use the following format &sort_by[]=popularity:desc&sort_by[]=rating:desc&sort_by[]=title:asc . When several sort_by are indicated the following order will be always applied: first by rating , next by popularity , next by title .

5) Next geo distance sorting will be applied where search results will be sorted by distance from a geo point &lat_lon= parameter (if indicated) to a nearest published/limited tourist attraction for tours and to Location for other object types. Please note, if &lat_lon= indicated and the geo sorting is made, objects without location ( geo_distance ) will be at the end of the geo sorted list.

6) Otherwise, last sorting will be by an internal immutable order.

HTTP Request

GET https://api.izi.travel/mtg/objects/search

An array of various MTGObjects (Museum, Tour, Collection, Navigational Story, Tourist Attraction) and City, Country objects. Or an empty array.

Error codes

See Generic Errors

Tours: search and return in short form

• Find “Baltimor” City example
• Filter and Sort Special Projects example
• Compact and Full Forms of MTGObjects.

Get MTGObject

Get English version:

Get English version in compact form including city section:

Get a MTGObject by UUID (Museum, Collection, Exhibit, Tour, Tourist Attraction, Navigational Story)

GET https://api.izi.travel/mtgobjects/:uuid

Query Parameters

An array with a MTGObject.

Get multiple MTGObjects

Get two objects:

Get MTGObjects by multiple UUIDs of MTGObjects. This endpoint considers only following types of objects: Museum, Tour, Tourist Attraction, Navigational Story, Collection, Exhibit. If you pass uuid of Publisher/City/Country, API will ignore it.

GET https://api.izi.travel/mtgobjects/batch/:uuid,:uuid,:uuid

An array of MTGObjects.

Get the number of MTGObject’s children

Get the number of children with enlish version of content:

Get the number of children of a MTGObject.

• For tour : tourist_attraction and story_navigation ,
• For museum : exhibit and collection ,
• For collection : exhibit , however, starting from API version 1.2.3 , story_navigation will be returned as well, see “Museum Tours” .

GET https://api.izi.travel/mtgobjects/:uuid/children/count

Amount of children of MTGObject with requested UUID as integer.

Get children of MTGObject

Get russian version of children:

Get children of the MTGObject.

• For collection : exhibit , however, starting from API version 1.2.3 , story_navigation will be returned as well and order of returned exhibits and story_navigations is important, see “Museum Tours” .

GET https://api.izi.travel/mtgobjects/:uuid/children

An array of MTGObjects (or empty).

Get Museum MTGObject by external IP address

Try to find a museum using its external IP address. IP address is detected by server.

GET https://api.izi.travel/mtgobjects/ip

An array with a MTGObject (or empty array).

Get parents of MTGObject

Get parents of 7061495d-f2bf-43e2-9f3b-e232b2a921b9 object that published and has published profile on en language:

Get parents of MTGObject.

If the object with provided uuid has not been found (does not depend on filtering parameters), 404 ‘Not Found’ will be returned. Otherwise an array of parents MTGObjects depending on filtering, like languages, publishing statuses etc. If there are no parents or do not follow filters, an empty array can be returned.

GET https://api.izi.travel/mtgobjects/:uuid/parents

An array of MTGObjects. If there are no parents or do not follow filters, an empty array can be returned.

Get list of Cities

Example: Get third and forth found cities with English content:

Get list of City objects that have content on requested languages.

GET https://api.izi.travel/cities

An array of city objects that have content on requested languages represented as a list of City objects in Full or Compact forms without translation section. Returns empty list of there are no matched cities.

Get “Amsterdam” City by uuid with translations:

Get City object by UUID.

GET https://api.izi.travel/cities/:uuid

City object represented in Full or Compact form. Returns 404 HTTP code if there is no City with provided UUID.

Get City’s children

Get second child of “Amsterdam” City:

Get City’s children (museums, tours)

GET https://api.izi.travel/cities/:uuid/children

Array of Tours and Museums which belongs to the city represented as a list of Compact or Full MTGObjects without city and country sections. Returns 404 HTTP code if there is no City with provided UUID.

Get the number of City’s children

Get the number of children of “Amsterdam” City for English and Russian content:

Resonse as integer:

Get the number of City’s children (museums, tours)

GET https://api.izi.travel/cities/:uuid/children/count

Number of children of requested City on requested languages (returned as an integer).

Get City’s Country

Get Country of “Amsterdam” City, first try to return in 'nl’, then 'en’ and finally in 'ru’ languages:

The same request as above, however, the result in compact form:

Get Country of City.

GET https://api.izi.travel/cities/:uuid/country

Country object represented in Full or Compact . Returns 404 HTTP code if there is no City with provided UUID or City does not have Country.

Get list of Countries

Example: Get Countries with English content and offset as 10:

Get list of Country objects which have content on requested languages.

GET https://api.izi.travel/countries

An array of Country objects that have content on requested languages represented as a list of Country objects in Full or Compact forms. Returns empty list if there are no matched countries.

Get Country

Get “Netherlands” Country by uuid for English version:

Get Country by UUID.

GET https://api.izi.travel/countries/:uuid

Country object represented in Full or Compact forms.

Get Country’s children

Get second child of “Netherlands” Country:

Get Country’s children (museums, tours)

GET https://api.izi.travel/countries/:uuid/children

Array of Tours and Museums which belongs to the country represented as list of Compact or Full MTGObjects without city and country sections. Returns 404 HTTP code if there is no Country with provided UUID.

• Get museums in “Baltimor” City example

Get Country’s Cities

Get Cities of “Netherlands” Country, first try to return in 'nl’, then 'en’ and finally in 'ru’ languages:

Get Country’s Cities.

GET https://api.izi.travel/countries/:uuid/cities

An array of City objects which belong to requested Country and have content on requested languages represented as a list of See City objects Full or Compact forms.

Get Publisher data

Example: Get “Amsterdam Museum” Publisher content: see Get Publisher example. Example2: Get “Amsterdam Museum” Publisher description - full form without children:

Get Publisher’s data (published museums, tours) by UUID.

• See /mtg/objects/search endpoint.

GET https://api.izi.travel/mtg/publishers/:uuid

Publisher object represented as Full or Compact Publisher object.

Get Publisher’s children

Get Publisher’s children (museums, tours)

• See Example Get Publisher’s Museums and Tours

GET https://api.izi.travel/mtg/publishers/:uuid/children

Array of Tours and Museums which belongs to the publisher as a list of Compact or Full MTGObjects. Returns 404 HTTP code if there is no publisher object with provided UUID.

Get the number of Publisher’s children

Get the number of children of “Amsterdam Museum” Publisher for en and nl languages:

Get the number of Publisher’s children (museums, tours)

GET https://api.izi.travel/mtg/publishers/:uuid/children/count

Number of children for requested languages (returned as an integer).

Get Languages of Publisher’s children

Get Publisher’s content languages:

Returns an array of languages where Publisher has content (museums and tours).

GET https://api.izi.travel/mtg/publishers/:uuid/children/languages

An array of languages or empty (if there are no content in languages parameter).

Website Featured Content

Example: Get featured content for nl language:

The endpoint provides current featured content (Editor Choice): promoted or most popular tours , museums and cities . This is a special endpoint mostly used on izi.TRAVEL site.

Another promoted content are Special Projects that used to create an interest to outstanding content or special actions in certain region (see FILTERS (SEARCH SCOPE) and SORTING sections in /mtg/objects/search end-point).

The end-point returns the following sets of objects for a requested language:

• A primary set of museums and tours indicating position of a content in izi.TRAVEL dashboard (see position field in response). The position value can be [1..5], however, the primary set does not always keep content for all position values.
• A secondary set of museums and tours where the position is not provided. The secondary set is used for cases when a dashboard has more than 5 places or when the primary set does not have content with certain position value.
• A set of cities (without position ) used for showing a city in a dashboard. The showing of cities can be in random order, for example, in time-based or refresh-based manner in some place of a dashboard.

GET https://api.izi.travel/featured?

An array of objects:

Featured Content Images

An image object format is the following:

A featured Museum or Tour can have one image with type image , when City can have cover in additional to image type.

URL pattern to access an image is {MEDIA_BASE_URL}/featured/{IMAGE_UUID} , where:

• MEDIA_BASE_URL is https://media.izi.travel
• IMAGE_UUID is uuid of the image in izi.Directory.

Examples of images URLs:

• City’s cover https://media.izi.travel/featured/547beba9-5485-42c4-b2cf-906950cc2bb3
• Tour’s image https://media.izi.travel/featured/78fbaeb7-95e4-44dd-8028-0b3f99b1fa11
• Apps Featured Content

Example: Get featured content for en language sorted by distance:

The endpoint provides current featured content for izi.TRAVEL Applications (Editor Choice): promoted or most popular published tours , quests and museums .

The end-point returns only published content in order defined by a featured content publisher or sorted by distance if &lat_lon= parameter is indicated ( position field in response reflects the ordering as well). Note: returned content can be paid . The maximum number of returned objects is 10.

A client shall request featured content indicating preferred language or set of preferred languages via parameter &languages , for example, &languages=nl,ru . If there is no set defined for the first nl language or there is no published content for the language, the end-point will try to return featured content set for next language ru , and so forth. If there are no featured content for the set of passed languages, the end-point will try to return set for en language. HTTP error 404 will be returned when no appropriate featured content are published (including en ).

GET https://api.izi.travel/featured/mobile?

A featured Museum or Tour has at least one image with type featured .

Example: https://media.izi.travel/featured/28a4f4e1-f5c7-438c-9a5d-df85d9722895

Rating & Reviews

Get reviews.

Get all reviews for “Rijksmuseum” example:

Returns ratings average and reviews for museum , collection , exhibit , tour and tourist_attraction . The end-point returns only records with reviews where newest record goes first.

GET https://api.izi.travel/mtgobjects/:uuid/reviews?

For success cases (HTTP response is 200)

Metada section, data section, paging section, for error cases (http response is not 200), get error codes, post reviews.

Post rating/review for “Rijksmuseum” example:

Post rating/review for museum , collection , exhibit , tour and tourist_attraction .

POST https://api.izi.travel/mtgobjects/:uuid/reviews?

HTTP Header

Request parameters, post error codes, get ‘used’ languages.

Get 'Used’ languages:

Returns the languages list of existent content in izi.TRAVEL Directory. The list can be used for retrieving any reachable content using &languages= parameter in API requests.

Note: starting from API version 1.2.4 , any keyword can be used in &languages= parameter and any means any language from the 'Used’ languages, see Languages section.

Note: the list of languages has predefined order.

GET https://api.izi.travel/languages/used

An array of languages where content exists in izi.TRAVEL Directory.

• /languages/supported

Get 'Supported’ Languages

Get 'Supported’ languages:

'Supported’ are all available languages in izi.TRAVEL Directory for creation and publishing content, however, only part of these languages is used, to get the list of languages where content exists, you shall use /languages/used end-point.

GET https://api.izi.travel/languages/supported

An array of languages available in izi.TRAVEL Directory to publish content.

• /languages/used

Detect object presence by some UUID

Example: Get type of object for UUID ‘768fefbb-fae5-41ba-bfd9-7b708d80cc65’

For some cases, API clients would like to detect an object presence in izi.DIRECTORY by some UUID, then retrieve the object using corresponding API end-point, ignore it or process according to the client specific cases. The end-point returns object(s) presence for passed uuid , the end-point does not take into account object’s statuses, languages, etc.

GET https://api.izi.travel/mtg/objects/:uuid/presence?

An empty array if no objects found, otherwise an array of objects:

Media for Recognition

Get object’s media (images) for recognition:

Get media (images) for training classifiers or for machine learning to detect individual izi.TRAVEL objects.

GET https://api.izi.travel/mtgobjects/:uuid/media_for_recognition

Get a tourist attraction

This request shows an example of an tourist attraction in full form with the following sections:

• Trigger Zones
• Content – Audio – Images – Quiz

This request shows an example of tours search in Amsterdam:

Around 10 km

Language: en

Returns first five tours in short form

Response includes geo_distance and location of tours

See /mtg/objects/search for details.

Get a museum without children

This request shows an example of a museum in full form without children section. The following sections are provided:

• Content – Audio – Images – Video

Find museum by name

This request shows an example of search of “The Walters Art Museum” museum.

This request shows an example of receiving of a museum object indicating what kind of objects (sections) shall be included in response, see includes=download,city&except=publisher,children part of query.

This request shows an example of receiving of a museum object indicating what kind of objects (sections) shall be included in response, see includes=all,city,country&except=translations,publisher,download part of query.

Find “Baltimor” City

This request shows an example of receiving the “Baltimor” City object for English and Russian languages indicating that translations section shall be included into response.

Get museums in “Baltimor” City

The request shows an example of receiving museums of “Baltimor” City.

Get Publisher

The request shows an example of receiving “Amsterdam Museum” Publisher content.

• Search for resources in izi.TRAVEL Directory.
• Example Get Publisher’s Museums and Tours

Get Publisher’s Museums and Tours

The request shows an example of receiving “Amsterdam Museum” Publisher museums and tours via search end-point.

Filter and Sort Special Projects

This request shows an example of filtering and sorting Special Projects in Hillegom city (Netherlands). Specail Projects are used to create an interest to outstanding content or special actions in certain region.

See FILTERS (SEARCH SCOPE) and SORTING sections. /mtg/objects/search for details.

Document Changelog

August-2020.

• An ability to filter random tours (not quests) by category during search has been added. See &tours_categories= parameter in /mtg/objects/search end-point.

February-2020

• An ability to get Apps Featured Content (Editor’s Choice) sorted by destination is added to /featured/mobile end-point. See &lat_lon= parameter.

- /mtgobjects/:uuid/media_for_recognition end-point added for retrieving media (images) that should be used for training classifiers or for machine learning to detect individual izi.TRAVEL objects.

January-2019

• An ability to filter and sort Special Projects (another promoted content) was added to /mtg/objects/search end-point. See FILTERS (SEARCH SCOPE) and SORTING sections.
• Filter and Sort Special Projects example added

September-2018

• Content Caching section has been added.
• Minor corrections.

November-2017

• See Media Access , IMAGE (CITY).
• See images in City’s Compact and Full forms.
• Description of City’s desc field was updated. See City Full Form .
• visible field was deprecated in City’s Compact and Full forms.
• High Level Models (diagrams) section has been extended.
• Descriptions corrections.

January-2017

• High Level Models (diagrams) section has been added.
• Publishers end-points marked as deprecated (will not be supported in future), /mtg/objects/search end-point shall be used instead with Publishers scope and other filtering/sorting options.

August-2016

API version 1.8 introduced where new tour’s categories have been added.

• running (10 km/h), train (60 km/h), horseriding (10 km/h)
• See Versioning , MTGObject Full Form , MTGObject Compact Form , Apps Featured Content

/mtg/objects/:uuid/presence end-point is available to detect object presence by some UUID.

API version 1.7 introduced (see Versioning changelog) where the children_count field in City/Country objects (both forms) will not be returned starting from this version.

Internal behavior changed:

• Stripping diacritics and HTML tags in query as well as search in all Country/City translations, see Search for MTGObjects, Cities and Countries , chapter Query (Full Text Search)
• Changed order of languages in Used and Supported languages: ru language shifted from second to eighth position.

Document updates:

• bounds field in Map is marked as typical for museum and tour , but not mandatory (can not be returned)
• Clarifications added: geo_distance returned field is optional, in case of sorting by geo_distance , objects without geo_distance field will be at the end of sorted list, see Search for MTGObjects, Cities and Countries , chapters ‘Current geo distance’ and 'SORTING’.
• New overview section Parameters has been added.
• Order of API version and password clarified when passed via parameter or HTTP header, see Versioning and Limited content access
• Generic Errors extended

Recomended tour’s categories average speeds changed:

• API version 1.6 introduced, see Versioning changelog.

/mtg/objects/search end-point extended (see details in the end-point description):

• short form introduced in additional to compact , it allows to improve performance of API calls by reducing traffic;
• quest or random tours filtering added;
• the search geo-area can be set by arbitrary bounding box using parameter &bbox= (for exclusion using parameter &ex_bbox= );
• &geo_search_type= parameter added for geo-search area filtering;
• current geo distance in meters and tours locations (locations of published/limited tourist attraction) can be added to filtered content in responses;
• fwm=true parameter added to filter content for Free Walking Mode (FWM);
• search results for any API versions will be sorted by distance from a geo point &lat_lon= parameter (if indicated) to a nearest published/limited tourist attraction for tours and to Location for other object types, see 'SORTING’, p.4
• last sorting from geo point '0.0;0.0’ replaced by an internal immutable order, see 'SORTING’, p.4

sequential tours are not supported from 16Q1, only random and quest tours;

location of random tour is now location of its first tourist attraction instead of center of tour’s map bounds,

HTTPS access comments added in Media Access section.

• API version 1.5 introduced, see Versioning changelog.
• duration field returned for museum’s collection if it set and indicated API version is 1.5 or above. See MTGObject Full and MTGObject Compact forms.
• Sizes of 1600x1200 images version are included (in additional to 800x600) to size (see MTGObject Full Form ) if indicated API version is 1.5 or above.
• Added notes about HTTPS access to media directory (see Media Access )

18-Feb-2016

• 1600x1200 resolutions of images are available. See Media Access , IMAGES (STORY), IMAGE_SIZE.
• API version 1.4 introduced, see Versioning changelog.
• Filtering by quest type ( tour with playback type quest ) added to /mtg/objects/search for API version 1.4 or above.
• Filtering and sorting by ratings added to /mtg/objects/search for API version 1.4 or above.
• Added ability to include/exclude route field to/from MTGObject Compact Form , see Includes/Except for API version 1.4 or above.
• Added end-point to retrieve parents of a MTGObject, see /mtgobjects/:uuid/parents .
• parent_uuid in MTGObject Full Form marked as deprecated.

05-Nov-2015

• Off-line packages will not be supported from 15Q4, see Download section.
• API version 1.3 introduced, see Versioning changelog.
• New 'open-ended question’ quiz type introduced, see Quiz .
• quest playback type introduced starting from API version 1.3 , see Quests overview, Playback section, Segment and Conditions .
• playback_type field is returned for museum , collection and tour objects for API version 1.3 or above. See MTGObject Full , Compact forms and Playback section.
• playback_type field is returned for museum and tour in /featured/mobile end-point for API version 1.3 or above.
• form parameter is deprecated in /mtg/objects/search , returning objects in full form will be switched off till the end of 2015 year.
• DEPRECATED children_count field in City/Country objects will be excluded till the end of 16H1, see City’s Compact and Full forms; Country’s Compact and Full forms
• Field closing_line added to Full Form of Museum/Collection/Tour MTGObjects for API version 1.3 or above, see sections Content and Versioning .

28-Jul-2015

• YouTube video link is supported starting form API version 1.2.5 . See Media , section C), and Versioning .
• Images fot Website Featured content location changed, see Website Featured Content , section FEATURED CONTENT IMAGES

04-Jun-2015

• Search detailed description added to /mtg/objects/search .
• API version 1.2.4 introduced, see Versioning changelog
• Search in Publishers feature added from API version 1.2.4 , see /mtg/objects/search .
• Languages description added and any keyword declared for &languages= parameter from API version 1.2.4
• New end-points /languages/used and /languages/supported are declared.
• Clarifications added to /cities and /countries end-points: City/Country are available when at least one published museum or tour exists in City/Country. If City/Country will not have at least one published museum or tour in the future, for example, Content Providers changed status from published .
• children_count field in City/Country objects marked as DEPRECATED.
• sort_by parameter described in /mtg/publishers/:uuid and /mtg/publishers/:uuid/children .

05-May-2015

• /featured/mobile end-point declared: “Get featured content for izi.TRAVEL Applications”.

30-Apr-2015

• User Generated Data section added.

28-Apr-2015

• API version 1.2.3 introduced, see Versioning : “Museum Tours” feature is declared; title field returned for story (common) images, see Media .

22-Apr-2015

• HTTP Compression section added that describes method to improve transfer speed in additional to Includes/Except feature.
• API version 1.2.2 introduced, see Versioning : vk ( https://vk.com/ ) field added to Publisher’s Contacts ; Sponsors in MTGObject Full Form

07-Apr-2015

• City, Country, Publisher added to MTGObject Compact and Full forms
• 422 error code added to Generic Errors .
• Rating & Reviews feature added: end-point /mtgobjects/:uuid/reviews , section Reviews declared, reviews added to Includes/Except , MTGObject Compact and Full forms.
• Field news added to Full Form of Museum’s MTGObjects, section Content and Includes/Except
• Parameter type documented in Get City’s children and Get Country’s children to retrieve only museums or tours.
• Parameters audio_duration and children_count_in_full_form set to boolean value. See Endpoints .
• audio_duration , children_count fields descriptions added to MTGObject Compact form and to Content of Full form.
• Clarified Purchase for museum MTGObject Compact and Full formsand supported API version .
• Image for City described: see Media in City’s Compact and Full forms, and IMAGE (CITY) in Media Access
• Field contacts reflected in MTGObject Full form.
• Includes/Except clarifed and parameters includes/except in endpoints .
• Media Access updated for Publisher’s Cover.
• Quiz reflected in MTGObject Compact form.
• children_count added to Country Full and Compact forms.
• size added to MTGObject Full form.

06-Feb-2015

• Website Featured Content endpoint description added.
• Publisher Contacts corrected in Publisher Full Form .
• UI style of left navigational bar tailored.
• Minor UI fixes for browsers on mobile devices.
• Response of example Get Publisher’s Museums and Tours corrected.

01-Feb-2015

• Includes/Except description added to Overview chapter.
• Endpoints summary table added.
• product_id field has been removed from Purchase object.
• Document cross-references updated.

7 of the best all-inclusive experiences to book this year, from a travel planner

• As a travel planner, my clients seem to be increasingly interested in all-inclusive trips .
• Some of my favorite luxury resorts are in Costa Rica, the Maldives, and Isla Mujeres.
• Cruises, group tours, and adults-only lodgings can also come with all-inclusive options. 

As a travel planner at Marvelous Mouse Travels , I know vacations are expensive — especially if you're looking to go somewhere this summer . But all-inclusive travel is often a great way to get the most value out of a luxury experience.

I've been on several all-inclusive vacations with my family, friends, and work, and I've helped other people book them in destinations around the world .

Here are some of the best all-inclusive experiences I'm recommending to my clients this year.

Try a split-stay vacation to see the best of Costa Rica.

Costa Rica is one of the most sought-after vacations , and for good reason. It's great for both relaxation and adventure.

I recommend booking a split stay, starting at an all-inclusive resort in Guanacaste near the beach for some fun in the sun and moving to a resort near the famous Arenal Volcano for a jungle adventure.

Some of my favorite resorts in Costa Rica are the Westin Reserva Conchal and the Dreams Las Mareas. And if you're looking for an even more unique experience, check out the glorious swim-out suites with private pools at Dreams.

Baglioni Maldives is one of my favorite all-inclusive resorts.

The Maldives, a remote set of islands in the Indian Ocean, offers a plethora of resort options for couples and families, but Baglioni Maldives is my favorite.

For many in the US, getting to the islands can be daunting — there are very few direct commercial flights, and it can take almost an entire day. But it's hard to beat the country's luxury accommodations and gorgeous landscape.

The Maldives also has some of the most beautiful marine life and coveted spots for snorkeling and scuba diving.

No matter where you go, overwater bungalows are the ultimate all-inclusive splurge.

Overwater bungalows — villas standing on poles over open ocean water — are prevalent at all-inclusive resorts in destinations like the Maldives, Fiji, and Bali.

But I've also come across the luxurious accommodations at select adults-only Sandals Resorts throughout the Caribbean.

I think having a private villa on the water is the perfect way to unwind and relax.

Adults-only vacations are on the rise.

Traveling with kids can be a blast, but I also think it's important for adults to take a much-needed break on their own.

Adults-only resorts have been a total respite for me and my husband after hectic months of juggling work with our kids' school and sports schedules.

If you're looking to unwind with a partner, relax on a girls' trip, or even connect with your adult children, there are countless adults-only, all-inclusive resorts to choose from, depending on where you're looking to visit.

Some properties, including Sandals and Beaches Resorts, also offer butler service. Designated staff members can help with anything from room requests and dining reservations to cabana rentals and transportation coordination.

I upgraded to the service at my favorite adults-only spot, Le Blanc Los Cabos, and I felt totally pampered.

Isla Mujeres is pure luxury.

Isla Mujeres, a small island off the coast of Cancún, is known for its crystal-clear, turquoise water and peaceful vibe. It's also home to Playa Norte, one of the best beaches in Mexico .

Impressions Isla Mujeres by Secrets is a gorgeous all-inclusive resort on the island. It offers luxury at its finest, but with only 125 rooms, it has a boutique feel.

One of my favorite features of the resort is the waterslide that leads right into the beautiful ocean.

There are plenty of all-inclusive packages at sea.

Cruising is one of the most popular vacations , whether it's an epic adventure on a Royal Caribbean Cruise, a couples-only journey on Virgin Voyages, or a regal tour of Europe on Viking River Cruises.

Although cruises aren't traditionally considered all-inclusive, with the right booking, they can have the same feel as a luxury resort.

Most cruise bookings include food, nonalcoholic drinks, and live entertainment. If you add beverage packages and excursions in advance, your trip should be fully paid for before you depart.

Book a small-group or private tour if you're looking for adventure.

Group travel is a great way to explore new places while soaking up culture and history.

Popular destinations include Italy, Japan, Costa Rica, and Alaska, and many travel companies take care of everything for you, essentially making it all-inclusive.

I like Adventures by Disney , which offers small-group travel all over the world facilitated by seasoned guides. All the trip details are taken care of, including experiences, food, lodging, and transportation.

Additionally, Kensington Tours offers luxury private travel where every facet of the trip is meticulously planned for you.

• Main content

Meta working on travel mode for using Quest headsets during flights after Vision Pro launches with feature

Today I learned two things. First, apparently Meta Quest headsets don’t work on planes? I guess Apple knew to prioritize that feature for Vision Pro. And second, support is reportedly on the way. Add this to the list of ways competition from Vision Pro is making Meta Quest 3 a better product.

For April, Meta released software update v64 that makes Quest 3 passthrough more like Vision Pro, users say. Motion blur is more noticeable, but still clarity is increased. Meta has also added support for viewing spatial videos captured from iPhone 15 Pro.

Now Meta may be planning to introduce flight support as soon as v65 next month. Per @Lunayian on X ( via Nicholas Sutrich ), several code strings reference travel mode for use on a plane.

Early NUX render to introduce "Flight Mode" I found in Meta Quest OS v65 pic.twitter.com/oq2GzCiaZu — Luna (@Lunayian) April 18, 2024

Apple pushes watching movies and TV shows during flights as a key use case for Apple Vision Pro. It’s one of the first things you see at the top of Apple’s website currently.

Surely Meta has taken notice and prioritized travel mode as it positions Meta Quest 3 as a dramatically cheaper solution to Vision Pro with many of the same capabilities.

The most impactful change, however, would be around multitasking. Quest headsets are limited to three app windows at a time right now. Apple Vision Pro has plenty of other limitations, but there’s virtually no limit to how many windows can be placed around a room and used together.

• Zuckerberg says Meta Quest 3 is better than Apple Vision Pro
• Apple Vision Pro is already making the Meta Quest 3 better
• Vision Pro latency by far the best on passthrough; lags behind Meta on angular motion
• Meta confirms spatial video playback coming to Quest one day before Vision Pro launch

FTC: We use income earning auto affiliate links. More.

Check out 9to5Mac on YouTube for more Apple news:

Zac covers Apple news, hosts the 9to5Mac Happy Hour podcast, and created SpaceExplored.com.