It has nothing to do with travel. The only thing it does is load one script — the same line an affiliate would paste into their own site. The launcher in the corner is the widget.
Copied
The launcher in the corner is a real widget, not a mock-up. It is loaded
with as its platform and
as its API, and every search it runs is a
live one against that platform.
| Attribute | What it does |
|---|---|
data-platform | Which seller platform this embed sells for, e.g. seller.example.com. |
data-api | The API that serves that platform. Must be https. |
data-affiliate | The referral code every outgoing link carries. Without it the search still works, but no booking is credited. |
data-side | right (default) or left — which edge the launcher sits on. |
data-offset | Distance from the corner in pixels. Default 24. |
data-accent | Any CSS colour, for the button, the active tab and prices. |
data-lang | en or fa. Defaults to the page's own <html lang>. |
data-dir | ltr or rtl. Follows the language unless set. |
data-products | Which tabs to offer, comma separated: flight,hotel,activity,tour. |
data-open | Which tab opens first. |
data-label | Text on the launcher. none makes it a round icon button. |
The travel API works out which platform a request belongs to from the
request's Origin header. A browser sets that to the page's
own host and forbids scripts from changing it, so a call straight from
this page would arrive labelled with this domain and be rejected. The
proxy behind /api presents the platform domain instead,
which is what lets one widget work on any number of unrelated sites.