Accor ALL Hotel Scraper
Pricing
from $2.54 / 1,000 hotels
Accor ALL Hotel Scraper
Searches Accor ALL (Sofitel, Novotel, Mercure, ibis, …) for hotels in a destination with live cash rates, ratings, location and photos, via the reversed Accor mobile GraphQL API. Read-only public hotel data; no account needed.
Pricing
from $2.54 / 1,000 hotels
Rating
0.0
(0)
Developer
R.L.
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
0
Monthly active users
19 days ago
Last modified
Categories
Features
Share
Search Accor ALL hotels (Sofitel, Pullman, Novotel, Mercure, ibis, and the rest of the group) for a destination and get structured results with live cash rates, star and guest ratings, location, distance and photos. The actor talks to Accor's mobile BFF GraphQL API directly (reversed from the Accor Android app), using the public (no-account) tier.
Input
| Field | Type | Notes |
|---|---|---|
destination | string | City or area, e.g. Paris. Resolved via Accor's own location search. |
checkIn / checkOut | date | Absolute (YYYY-MM-DD) or relative (30 days). Empty → +30d / +3 nights. |
adults | integer | Adult guests. |
currency | string | ISO currency (EUR, USD, GBP, …). |
countryMarket | string | Two-letter market used for pricing (FR, GB, US, …). |
includeDetails | boolean | Add amenities, photos and reviews per hotel (extra calls, billed separately). |
maxItems | integer | 0 = all hotels for the destination. |
proxyConfiguration | proxy | Residential proxy required — defaults to Apify RESIDENTIAL. |
Output
One row per hotel: id, name, brand, stars, guest rating + review count, member and standard price,
currency, meal plan, availability, distance from the search point, GPS, country and a hero image.
With includeDetails, each row also carries description, amenities, images, reviews and a
maps URL.
Why a residential proxy is required
Accor's BFF stalls requests from datacenter IP ranges, so the actor routes through a residential proxy (Apify RESIDENTIAL by default). A datacenter proxy or no proxy will hang.
Pricing
Three events, charged for what a run actually delivers:
| event | charged |
|---|---|
hotel | once per hotel in the search result |
hotel-details | once per hotel whose enrichment brought content back — an enrichment where every Accor sub-call failed leaves a shell row, which is delivered and not charged |
review | once per guest review returned, and only with includeReviews on |
They are additive: a hotel asked for with details and ten reviews bills hotel + hotel-details + ten review events.
The current price of each is on the Pricing tab of this Actor's page in Apify Store. That tab is generated from the Actor's own pricing record, so it is always current, and your plan's rung is applied automatically. A figure repeated here would be a second copy that drifts out of date.
Whether Apify platform usage (compute units, proxy traffic, data transfer) is billed on top of the per-event price is shown on that same Pricing tab, and on your run's usage tab once it has run. Accor stalls datacenter IPs, so this Actor needs a residential proxy; where usage is passed through, that traffic is billed by the gigabyte and is usually the larger line item on a big run.
A run that finds no available hotels, or that is rejected for bad input, charges nothing. You can cap what any single run may spend with Max total charge, with no minimum — and a run stopped by that cap says so in its status message rather than ending quietly with a short dataset. Every run also leaves a BILLING_AUDIT record in its key-value store: what it charged, per event, against what it delivered.
Notes
- Public cash rates only; loyalty-point pricing needs an Accor member login and is out of scope.
- Unofficial client, not affiliated with or endorsed by Accor.