Expedia Rapid API: Who Gets Access and What It Covers
This guide covers what the Expedia Rapid API includes, who qualifies for access, and the open route to Expedia hotel rates and reviews.
Table of contents

The Expedia Rapid API is the real thing: a documented, mature lodging API from one of the largest travel companies in the world.
That's exactly why the disappointment stings.
Rapid exists for partners who sell travel, and the key that makes the documentation useful is gated behind a commercial qualification process.
Most developers who search for it (needing rates, availability, or reviews data) don't fit the profile and won't get through.
This guide covers what Rapid actually includes, who qualifies, and the open route to Expedia hotel data when a booking partnership isn't your business.
Key Takeaways
- Rapid is Expedia Group's lodging supply API: content, rates, availability, and booking for hundreds of thousands of properties, built for travel sellers who transact.
- The key is the gate, not the docs. Rapid's documentation is publicly browsable, and getting credentials requires a partner application with a business case and projected booking volume.
- Data-only use cases don't qualify. Rapid monetizes through bookings, so market analysis and monitoring projects are outside its model, the same wall we mapped for the Booking.com API.
- Rates and reviews have an open route. Data APIs return Expedia room rates (including member-price deals) and guest reviews per property, no partnership required.
- Match the door to the job: building a booking product → apply for Rapid; reading Expedia data → skip the application entirely.
What the Rapid API Actually Is

Rapid is Expedia Group's B2B lodging supply API, documented on the Expedia Group developer portal.
What it covers, per Expedia Group's own materials: property content, live rates and availability, and booking flows for roughly 700,000 properties worldwide, the same supply that powers Expedia's own brands.
It's genuinely good at what it's for.
If you're building a travel product that sells stays (an OTA, a loyalty booking portal, a super-app travel tab), Rapid is one of the few serious supply options on the market.
The design assumption runs through everything: you will transact.
Rate access, content licensing, and support tiers all assume bookings flow through your integration.
Rapid is a revenue partnership with an API attached, and Expedia Group evaluates it as one.
Who Qualifies for a Rapid API Key

The application asks the commercial questions: what you're building, your business model, and your projected booking volume.
Expedia Group reviews applications against revenue potential, and agreements follow for partners who clear the bar.
Practical implications, stated plainly:
A funded travel startup with a booking product and volume projections has a real shot.
An established brand adding travel inventory has a strong one.
A developer who needs rate data for a comp-set dashboard doesn't fit the form's questions, and a data team monitoring review scores fits them even less.
Those applications tend to stall or go unanswered, and weeks spent waiting on them are weeks lost.
Searches for an "Expedia API key" almost always mean this qualification wall.
There's no self-serve key at any price, and no data-only tier of Rapid to apply for.
What Rapid's Docs Cover vs What Data Teams Need
Browsing Rapid's public docs and needing Rapid's capabilities are different things.
| You Need | Rapid's Answer | Practical Route |
|---|---|---|
| Booking capability | Yes, core product | Apply for Rapid |
| Live rates for arbitrary hotels | Partners only | Data API |
| Guest reviews | Partners only, own-integration scope | Data API |
| Property content at scale | Partners only, licensing terms | Data API |
| Market/comp-set monitoring | Outside the model | Data API |
The pattern repeats across every Expedia Group surface: the traveler-facing data you can see in a browser has no official read API, because the official APIs exist to power sellers, not observers.
Getting Expedia Hotel Data Without Rapid

Three routes, and the first one is only listed for completeness.
Applying anyway costs weeks and fits only genuine booking businesses.
Scraping Expedia works about as well as scraping any major OTA: aggressive bot detection, frequent markup changes, ongoing maintenance you own.
A data API returns the traveler-visible data as documented JSON.
The Expedia API from StayAPI covers the two surfaces data teams ask for: room rates and guest reviews.
Here's a real rates request for property 10507369 (an Aloft in the US):
curl -X GET "https://api.stayapi.com/v1/expedia/hotel/rates?property_id=10507369&check_in=2026-05-01&check_out=2026-05-03&adults=2" \
-H "x-api-key: YOUR_API_KEY"
The response (truncated):
{
"property_id": "10507369",
"sold_out": false,
"lowest_price_amount": 189.0,
"rooms": [
{
"room_name": "Aloft King Room",
"rate_plans": [
{
"deal": "Member Price",
"payment_model": "PAY_LATER",
"nightly_rate_amount": 189.0,
"total_price_amount": 378.0,
"strikeout_price_amount": 420.0,
...
}
]
}
]
}
| Field | Description |
|---|---|
lowest_price_amount |
Cheapest available rate for the stay |
rooms[].room_name |
Room type as Expedia displays it |
rate_plans[].deal |
Deal label, including Member Price |
strikeout_price_amount |
The crossed-out reference price |
payment_model |
Pay now vs pay later |
The deal field deserves a highlight: member-price rates arrive in the data, the discounted rates Expedia normally shows only to logged-in users.
For rate-parity and comp-set work, that's visibility a browser session in incognito mode can't give you.
Full parameters are in the Expedia rates endpoint documentation.
| Rapid (official) | DIY Scraping | Data API (StayAPI) | |
|---|---|---|---|
| Who gets access | Qualified booking partners | Anyone | Anyone |
| Approval time | Weeks to months | None | None |
| Rates for arbitrary hotels | Own integration scope | Fragile | Yes, incl. member prices |
| Reviews | Not the product | Fragile | Yes, structured |
| Booking capability | Yes | No | No |
| Maintenance | None | Ongoing | None |
One honest row in Rapid's favor: if you need to actually book rooms, nothing below it on this table does that job.
Getting Started
- If you're building a booking product, start at Expedia Group's developer portal linked above and budget for the partnership process. That's the right door for that job.
- For rates and reviews data, sign up at stayapi.com. Free tier, no credit card, no application.
- Find your property IDs (from Expedia page URLs) and run the rates call above with your own dates.
- For a no-code pipeline, the Expedia rates to Google Sheets integration lands the data in a spreadsheet, and the same pattern feeds Looker Studio, Power BI, N8N, or Make.com. For portfolio-scale rate monitoring, book a demo call.
FAQ
What is the Expedia Rapid API?
Expedia Group's lodging supply API: property content, live rates, availability, and booking for roughly 700,000 properties.
It's built for travel sellers under commercial agreements, with booking volume as the underlying business model.
How do I get an Expedia API key?
Through the Rapid partner application, which evaluates your business case and projected bookings.
There's no self-serve key; for data-only use cases, data APIs issue keys on signup instead.
Is the Expedia API free?
No.
Rapid is a commercial partnership, and while its docs are free to browse, credentials come with an agreement.
Data APIs typically offer free evaluation tiers (StayAPI includes one).
Where is the Expedia API documentation?
On the Expedia Group developer portal, and it's publicly browsable.
Reading it is free; calling it requires partner credentials.
Can I get Expedia rates without being a partner?
Yes.
Data APIs return room-level rates for any Expedia property, including member-price deals and strikeout pricing, as structured JSON keyed by property ID.
Ready to simplify your hotel data?
Join other developers using StayAPI to build the next generation of travel applications. Get started for free today.