Best We Hotel guest reviews API

Pull Best We Hotel guest reviews as JSON.

Real endpoint paths, request parameters, response fields, and implementation notes for production integrations.

Start free with 50 requests View the API hub

Endpoints

The calls behind this workflow.

GET Best We Hotel Reviews /v1/bestwe/hotel/reviews

Implementation notes

What to preserve in production.

Best We reviews are especially useful when a mainland China property portfolio needs more context than a single aggregate score. The endpoint returns the original guest text alongside the review date, room type, travel purpose, category scores, moderated guest photos, helpful count, and any response published by the hotel. Use the filter parameter to page through all, positive, negative, or photo reviews without changing the response shape. For repeat ingestion, persist the review id and reviewedat timestamp, request pages in sequence, and keep the propertyid as the stable join key back to hotel details and direct rates. Review text is supplied in the language published upstream, so downstream sentiment pipelines should preserve the source text before translating or classifying it.

Example

Request and response shape.

example.json

{
  "request": {
    "path": "/v1/bestwe/hotel/reviews",
    "params": {
      "property_id": "JJ1089",
      "page": 1,
      "page_size": 10,
      "filter": "all"
    }
  },
  "response": {
    "success": true,
    "property_id": "JJ1089",
    "rating": 4.8,
    "total": 1420,
    "reviews": [
      {
        "id": "68d3a27addc4bb51baa32ccd",
        "rating": 3.0,
        "content": "太破旧了！",
        "reviewer_name": "31***33",
        "room_type_name": "高级双床房"
      }
    ]
  }
}

FAQ

Best We Hotel guest reviews.

How many Best We reviews can I request per page?

The endpoint accepts a page_size from 1 to 20 and returns pagination metadata for the next request.

Can I request only negative or photo reviews?

Yes. Set filter to bad or photos; all and good are also supported.