POST

API health

24h health
Normal
  • Healthy / normal
  • Available
  • Limited
  • Mostly down
Normal

Last 24 hours

Last 30 days

Collect guest reviews for one Expedia hotel. Each review has rating, post date, stay date, trip type, travel party and whether the stay was verified. Narrow by date with since and set the order with sort. Complete coverage of every review is not guaranteed.

Send POST https://api.everyinfra.com/api/v1/social with platform set to expedia and action set to reviews. Price $1.39 per 1,000 requests ($0.001389 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

Expedia Reviews reads guest reviews of one hotel from its Expedia page, or the matching Hotels.com page, given as url. Each row carries the title and text, the rating with its word label, when the review was posted and when the guest stayed, the number of nights, the trip type and who the guest traveled with, the liked and disliked tags they ticked, and whether the stay was verified, along with the hotel's name, ID and average guest score. Hotel operators, revenue managers and travel researchers use it to follow guest sentiment, compare properties and track recurring complaints.

stay_date tells you when the guest actually stayed, which can be well before posted_at, so use it to judge how current an experience is. verified marks reviews from confirmed stays; unverified ones deserve less trust. liked and disliked are left out when the guest ticked nothing, so read a missing list as no tags rather than as missing data. since keeps only reviews posted from a given date on, which suits scheduled pulls that fetch only what is new.

AI prompt

#
Please help me write a data collection script with the EveryInfra Expedia Reviews endpoint (expedia/reviews).

How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to expedia and action to reviews, and put the parameters inside params.
- Required parameters:
  - url: Accepts a single hotel page URL from Expedia or compatible Hotels.com links to fetch property profiles or reviews. It does not accept search result pages.
- Optional parameters:
  - reviews_from: Acts as a compatibility input for the review start date, accepting YYYY-MM-DD. When since is provided simultaneously, since takes precedence. It does not filter hotel stay dates.
  - since: Sets the lower date bound for hotel review queries using YYYY-MM-DD format, taking precedence over reviews_from. It does not filter hotel opening dates or car rental pickup periods.
  - sort: Review order for reviews: newest, relevance, top_rated, or most_helpful. (allowed: most_helpful / newest / relevance / top_rated)
  - limit: The most rows to return in this call, an integer from 1 to 200. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 20)
- Returns a list of records. Main fields of each record: id, text, title, rating, rating_scale, rating_label, posted_at, stay_date, author_name, trip_type, stay_duration, traveled_with; 22 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=expedia.
- Example request body:
{
  "platform": "expedia",
  "action": "reviews",
  "params": {
    "url": "https://www.expedia.com/Tokyo-Hotels-Park-Hyatt-Tokyo.h20264.Hotel-Information"
  }
}
- Price: $1.39 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

#
NameInTypeRequiredDefaultDescription
AuthorizationheaderstringYes-Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
platformbodystringYesexpediaPlatform identifier, fixed value.
actionbodystringYesreviewsCapability identifier, fixed value.
urlbody.paramsstringYes-Accepts a single hotel page URL from Expedia or compatible Hotels.com links to fetch property profiles or reviews. It does not accept search result pages. Car rental queries must pass full search URLs via the keyword parameter instead.
reviews_frombody.paramsdateNo-Acts as a compatibility input for the review start date, accepting YYYY-MM-DD. When since is provided simultaneously, since takes precedence. It does not filter hotel stay dates.
sincebody.paramsdateNo-Sets the lower date bound for hotel review queries using YYYY-MM-DD format, taking precedence over reviews_from. It does not filter hotel opening dates or car rental pickup periods.
sortbody.paramsstring (enum)No-Review order for reviews: newest, relevance, top_rated, or most_helpful.Allowed valuesmost_helpfulnewestrelevancetop_rated
limitbody.paramsinteger (1–200)No20The most rows to return in this call, an integer from 1 to 200. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge.

Code samples

#
bash
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "expedia",
  "action": "reviews",
  "params": {
    "url": "https://www.expedia.com/Tokyo-Hotels-Park-Hyatt-Tokyo.h20264.Hotel-Information"
  }
}'

OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

#
Captured October 24, 2026 at 18:28 (UTC) by calling this API with the parameters in the code sample above. results and count are that call's real response with personal information (names, handles, avatars, profile links, contact details) removed; the list keeps the first 2. id, billing and quota differ on every call, so only their shape is shown.
json
{  "id": "req_…",  "platform": "expedia",  "action": "reviews",  "results": [    {      "id": "70294428",      "text": "Nice little motel with great location.",      "title": "Nice little motel.",      "rating": 8,      "rating_label": "Good",      "posted_at": "2014-05-08T00:00:00+00:00",      "author_name": "•••",      "trip_type": "",      "traveled_with": "Traveled with family",      "verified": true,      "language": "en_US",      "hotel_id": "20264",      "hotel_name": "Channel Inn",      "hotel_url": "https://www.expedia.com/Tokyo-Hotels-Park-Hyatt-Tokyo.h20264.Hotel-Information",      "hotel_rating": 6.6,      "platform": "expedia",      "rating_scale": 5    },    {      "id": "70225987",      "text": "Very smelly older gentalmen at front desk very bad attitude .",      "title": "Poor condition",      "rating": 2,      "rating_label": "Terrible",      "posted_at": "2014-05-06T00:00:00+00:00",      "author_name": "•••",      "trip_type": "",      "traveled_with": "Traveled with partner",      "verified": true,      "language": "en_US",      "hotel_id": "20264",      "hotel_name": "Channel Inn",      "hotel_url": "https://www.expedia.com/Tokyo-Hotels-Park-Hyatt-Tokyo.h20264.Hotel-Information",      "hotel_rating": 6.6,      "platform": "expedia",      "disliked": [        "cleanliness",        "staff & service",        "property conditions & facilities"      ],      "rating_scale": 5    }  ],  "count": 20,  "billing": {    "charged": …,    "charged_usd": …,    "balance_after_usd": …,    …  },  "quota": { … }}

Response fields

#

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

FieldMeaning
idThe record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms.
textBody text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so).
titleTitle. null when the platform has no titles (for example text-only posts).
ratingRating. The scale varies by platform: rating_scale on the same row gives the maximum (usually 5; Booking, Douban, iQIYI and NAVER use 10). Convert with rating_scale before comparing across platforms, or the comparison can come out backwards.
rating_scaleMaximum of rating in the same row: 5 for five-star scales, 10 for ten-point scales. Present only when the row has a rating.
rating_labelKeeps the platform's own meaning
posted_atPublish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it.
stay_dateKeeps the platform's own meaning
author_nameAuthor's display name.
trip_typeKeeps the platform's own meaning
stay_durationKeeps the platform's own meaning
traveled_withKeeps the platform's own meaning
verifiedKeeps the platform's own meaning
languageContent language code (for example zh, en) as judged by the platform; it can be wrong.
hotel_idKeeps the platform's own meaning
hotel_nameKeeps the platform's own meaning
hotel_urlKeeps the platform's own meaning
hotel_ratingKeeps the platform's own meaning
platformSource platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).
likedKeeps the platform's own meaning
dislikedKeeps the platform's own meaning
image_urlsArray of image links in the platform's display order; absent when there are no images.
owner_responseThe business's public reply to this review: text, author_name and posted_at; absent when there is no reply.

FAQ

#

Which hotel link does url need?

#

The page of one hotel on Expedia, such as https://www.expedia.com/Tokyo-Hotels-Park-Hyatt-Tokyo.h20264.Hotel-Information, or the same hotel's page on Hotels.com. Search result pages list many hotels and do not work, and car rental links belong in Expedia Car rental quotes instead. The same hotel link also works with Expedia Details for the hotel's own record.

What is the difference between since and reviews_from?

#

Both set the earliest review date, written as YYYY-MM-DD. since is the main parameter and reviews_from an alternative name accepted for compatibility; when you send both, since wins. They filter on when a review was posted, not on the guest's stay or a check-in date.

How do I focus on reviews from travelers like my guests?

#

Group rows by trip_type, such as business, leisure or family, and by traveled_with, such as a partner, family, friends or traveling alone. Put rows where verified is true first, and set sort to most_helpful when you want the reviews other travelers found most useful at the top. stay_duration separates short stopovers from longer stays.

Errors and billing

#
401
Missing or invalid key.
402
Insufficient balance. Top up first.
422
Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
429
Per-minute request limit reached. Wait for Retry-After, then try again.
503
Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
200 empty
No data. No charge.

Errors

Official references

#

Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.

  • Expedia: Review scores, posting eligibility, and existing responses ↗

    Official Expedia guidelines distinguish individual review scores, displayed aggregate property scores, and car rental evaluation methods, while allowing reviews from certain travelers who attempted a check-in without completing a stay. This action only exposes rating and eligibility terms, without guaranteeing that returned values share a unified scale or reflect fully completed stays.

    Checked 2026-09-04

Google Analytics needs consent. Privacy