raw.fliggy.reviewsFliggy hotel reviews
https://api.qovia.ai/v1/raw/fliggy/reviewsGuest reviews of a Fliggy hotel, newest first, up to 100 per page, paginated with cursor. Each review has its score (10-point scale), text, time, reviewer nickname and id (also for anonymous reviews that carry one), IP region, check-in month, room type, trip type, sub-scores, photos and the hotel's reply. A page past the end or an unknown hotel returns an empty, unbilled list.
Typical uses: Review and comment analysis and social listening, e.g. finding what users praise and complain about most.
- Price
- $0.0015 / call$1.5 per 1k$1 per 1k after 5M a month
- Billing
- Charged only for successful, non-empty resultsthe charge is in meta.charged_usd
- Scope
raw:fliggyThe API key needs this scope- Rate limit
- NoneNo per-account or per-endpoint request limit
Parameters
Only these parameters are accepted; any other one returns 400.
hotel_idFliggy hotel ID (shid, 5–15 digits), e.g. 10052156
Pattern^[1-9][0-9]{4,14}$Example
10052156cursorPage number, from 1
Default1Range1–200
Response
A success is HTTP 200 with the shared envelope: request_id, data (this endpoint's data, see the example) and meta (the charge). An empty result is also 200, with meta.empty true, not charged, and data may be an empty structure or null.
Errors
| code | HTTP | Billing | Description |
|---|---|---|---|
scope_denied | 403 | Not charged | This API key lacks the scope the endpoint requires. |
endpoint_unavailable | 503 | Not charged | The endpoint is not available right now (no data source connected yet, or no price configured); nothing ran. |
invalid_params | 400 | Not charged | The parameters failed validation: a required one is missing, a type or format is wrong, an array has more items than allowed, an unknown one was sent, or the POST body is not a JSON object. An error in one parameter starts with its name (item_id: …); a missing or unknown parameter starts with params: …. |
insufficient_balance | 402 | Not charged | The balance cannot pay for this call; top up first. |
upstream_busyRetryable | 503 | Refunded | The data source is busy or cooling down; refunded. Retry after Retry-After. |
upstream_timeout | 504 | Refunded | The data source timed out; refunded. |
upstream_error | 502 / 503 | Refunded | The data source failed; refunded. |
upstream_rejected | 400 | Refunded | The data source rejected these parameters (well-formed, but not accepted); refunded. |
not_found | 404 | Refunded | The data source has no such item (deleted, or the ID does not exist); refunded. |
reservation_expired | 504 | Refunded | The call took too long and was refunded automatically; no data is returned. |
Any request can also fail authentication: 401 invalid_api_key, 403 account_disabled, 429 too_many_auth_failures.
Needs an account with a balance; playground calls are billed like API calls.