Expedia: OTA, Multi-Vertical Marketplace and Retail Profile
Model Expedia as a multi-vertical OTA and travel marketplace separately from Expedia Rapid.
Platform facts
- Platform type
- OTA
- Role / capability
- OTA · Travel marketplace
- Ecosystem layer
- Retail / Discovery · Booking / Transaction
- Turkey relevance
- Global / Turkey context
- Service status
- Active
- Ecosystem audience
- B2C · travellers · B2B · industry partners
- Business model
- Not yet verified
- Integration method
- Not yet verified
- Company
- Expedia Group
- Parent company
- Not yet verified
- Direct supplier participation
- No
- Developer documentation
- Not yet verified
- Pricing / availability model
- Not yet verified
- Booking ownership
- Not yet verified
- Attribution model
- Not yet verified
Commercial models and integration paths may belong to different partner programmes; access and market eligibility depend on provider approval.
Sources for these facts
How is this entity connected?
Follow the same entity across integration, architecture, comparison, research and glossary layers. Links are generated from content metadata and topic similarity.
Expedia is one of Expedia Group's consumer-facing flagship travel brands. It combines hotels, flights, cars, cruises and packages within a multi-vertical retail journey.
Expedia is not Expedia Rapid
Expedia is a consumer OTA. Expedia Rapid is a B2B API product exposing lodging content, shopping and booking capabilities to partner applications. They share a group but have different audiences, contracts and ownership boundaries.
Retail / Discovery role
Expedia combines search, merchandising and booking within one consumer surface, so it should carry both OTA and travel-marketplace roles.
Offer model
A travel offer is more than price. Seller identity, cancellation, payment timing, taxes, baggage/meal and package context need to survive into downstream booking.
See Expedia Rapid for the B2B API layer.
Evaluating this technology or provider approach?
We can assess integration, architecture and operational trade-offs against your requirements.
Sources
Related content
ENUYGUN: Turkey OTA and Travel Marketplace Profile
A profile of ENUYGUN's role in Turkey's travel-distribution ecosystem across flights, buses, hotels, car rental and transfers.
Explore →Obilet: Turkey OTA and Multi-Vertical Travel Platform
A profile of Obilet's OTA role in Turkey across bus, flight, hotel, car-rental, rail and ferry travel products.
Explore →Amadeus Enterprise APIs and NDC Integration Guide
Design Amadeus Enterprise API Portal and Travel Platform/NDC integrations around access, entitlement, offer/order lifecycle, servicing, quota boundaries and observability.
Explore →OTA vs Metasearch vs Travel Marketplace: Key Differences
Compare OTA, metasearch and travel-marketplace models by transaction ownership, supplier relationships, monetization, handoff and technical architecture.
Explore →Sabre Travel APIs Integration Guide
Design a Sabre integration with explicit shopping, provider-reference, booking and post-booking boundaries across travel-agency API workflows.
Explore →Turkey Metasearch Market: Public-Evidence Technical Map 2026
Map Turkey's travel metasearch and distribution ecosystem across OTA, metasearch, GDS, NDC, bedbank, channel-manager, CRS and booking layers using public evidence.
Explore →