Accor API: How to Get Availability, Prices, and Reviews Programmatically
This guide covers the working route to Accor hotel data: search, availability, price calendars, and guest reviews as JSON, across every Accor brand.
Table of contents

Accor has no public API.
The company behind Sofitel, Novotel, ibis, Mercure, Pullman, and Fairmont runs official integrations through distribution and loyalty partnerships, none of which have a developer signup page.
If you've been searching for an Accor API to check availability, track rates, or pull guest reviews, the official channels weren't built for you.
The data routes exist anyway, and for Accor they're unusually complete.
This guide covers what Accor offers officially, what data you can actually get for any Accor property, and two worked examples with real responses: a price calendar and guest reviews.
Key Takeaways
- Accor has no public developer API. Official integrations serve distribution partners, travel sellers, and the ALL loyalty ecosystem, under commercial agreements.
- The data route is the richest of any hotel chain we cover. Eight endpoints: search, details, rooms, price calendar, reviews, amenities, photos, and URL-to-ID conversion.
- One integration covers every Accor brand. Sofitel, Novotel, ibis, Mercure, Pullman, and Fairmont properties all resolve through the same search and the same hotel IDs.
- The price calendar is the standout capability. Per-date cheapest rates and availability for any property, the same data the chain-API pattern proved valuable for Marriott.
- Reviews come from verified post-stay feedback, including the hotel's own responses, which makes the review data unusually clean for analysis.
What Accor Officially Offers Developers
Accor's official technology partnerships fall into three buckets, and all of them are commercial.
| Route | Who It's For | What It Covers |
|---|---|---|
| Distribution partnerships | OTAs, travel sellers, GDS channels | Inventory and booking under contract |
| Property/connectivity systems | Hotels in the Accor network, their tech vendors | Managing your own property |
| ALL loyalty ecosystem | Program partners | Points, offers, member benefits |
The pattern matches every chain we've documented: booking and operations have official channels, market-data access doesn't.
Reading availability, prices, or reviews for properties you don't operate isn't a product Accor sells to developers.
Applications for the distribution route are commercial negotiations with volume expectations, typically measured in months.
For a data use case, they're the wrong tool.
What Accor Data You Can Actually Get

Third-party data APIs cover Accor's public surfaces as documented REST endpoints.
The Accor API from StayAPI is the deepest chain coverage in the catalog: eight endpoints against one hotel ID.
| Endpoint | What It Returns |
|---|---|
| Search | Properties near coordinates or a destination, with best offer per hotel |
| Hotel details | Property profile, star rating, location |
| Rooms | Room types and current offers |
| Price calendar | Cheapest available rate per date across a range |
| Reviews | Verified guest reviews with hotel responses |
| Amenities | Facility lists |
| Photos | Property photo URLs |
| URL-to-ID | Any Accor page URL converted to its hotel ID |
The brand point matters in practice: search results span the whole Accor family, so a single query returns the ibis and the Sofitel in the same market with the same schema.
For European comp sets especially, that's often the majority of the branded supply in one call.
Everything below uses two real properties: Sofitel New York (hotel ID 2185) and ibis Cavaillon (hotel ID 2179).
Worked Example 1: Availability and Prices by Date

The price calendar returns the cheapest available offer for each date in a range, with sold-out dates flagged.
curl -X GET "https://api.stayapi.com/v1/accor/hotel/price-calendar?hotel_id=2185&date_from=2026-09-01&date_to=2026-09-07" \
-H "x-api-key: YOUR_API_KEY"
The response (truncated):
{
"success": true,
"hotel_id": "2185",
"name": "Sofitel New York",
"brand": { "code": "SOF", "name": "Sofitel" },
"calendar": [
{ "date": "2026-09-01", "status": "AVAILABLE", "amount": 685.4, "formatted": "$686" },
{ "date": "2026-09-04", "status": "UNAVAILABLE", "amount": null },
{ "date": "2026-09-06", "status": "AVAILABLE", "amount": 411.8, "best_rate_label": "Best price" },
...
]
}
| Field | Description |
|---|---|
status |
AVAILABLE or UNAVAILABLE per date |
amount |
Cheapest rate for a stay starting that date |
best_rate_label |
Accor's own cheapest-date flag |
brand |
Which Accor brand the property belongs to |
Two things this enables that a booking page can't: sold-out dates are explicit data (the September 4-5 gap above is a signal, not a blank), and a 60-day range arrives in one call instead of 60 page loads.
Run it on a schedule and you have a rate and availability time series for any Accor property.
Full parameters are in the price calendar endpoint documentation.
Worked Example 2: Guest Reviews with Hotel Responses

curl -X GET "https://api.stayapi.com/v1/accor/hotel/reviews?hotel_id=2179&limit=5" \
-H "x-api-key: YOUR_API_KEY"
The response (truncated):
{
"success": true,
"hotel_id": "2179",
"score": 4.3,
"review_count": 387,
"reviews": [
{
"author": "Johan B. K.",
"rating": 4.5,
"text": "The hotel is well located, clean with friendly and helpful staff...",
"trip_type": "As a couple",
"responses": [ { "text": "Dear Johan B. K., Thank you for your kind feedback..." } ]
}
],
...
}
Accor's review pool is verified post-stay feedback rather than open submissions, and the hotel's reply arrives structured in the same record.
For reputation work, that pairing is the useful part: you can measure not just what guests say but which complaints each property answers, and how fast.
The property here is an ibis in provincial France, which is the brand-coverage claim made concrete: the same endpoint serves the Sofitel above and a budget property in Cavaillon.
Full parameters are in the reviews endpoint documentation.
What Teams Build with Chain Data

- Direct-vs-OTA rate comparison. The price calendar gives you the chain's own rate; OTA endpoints give you the same room on Booking.com. The gap between them is the money conversation, and our rate parity guide covers how to monitor it.
- Comp sets that include branded supply. A market analysis that skips Accor properties misses much of Europe's inventory. One search call brings the whole family into the same schema as your OTA data.
- Portfolio review monitoring. Score trends and response rates across every property a management group runs, ibis to Sofitel, in one dashboard.
- Availability-based demand signals. UNAVAILABLE dates across a market's Accor properties are an occupancy proxy competitors can't see on a booking page.
Getting Started
- Sign up at stayapi.com. Free tier, no credit card, no partnership application.
- Find your hotel IDs: run a search by coordinates or destination, or paste any Accor property page URL into the URL-to-ID endpoint.
- Make the two calls above with your own properties and dates.
- Schedule the price calendar call (daily or weekly) to build your rate history, and pipe the JSON into your database, Google Sheets, Looker Studio, Power BI, or no-code platforms like N8N and Make.com. For portfolio- or market-scale projects, book a demo call.
FAQ
Does Accor have a public API?
No.
Official Accor integrations run through distribution, connectivity, and loyalty partnerships under commercial agreements.
Third-party data APIs are the route for reading availability, prices, and reviews programmatically.
Which Accor brands does the data cover?
The whole family resolves through the same endpoints: Sofitel, Novotel, ibis, Mercure, Pullman, and Fairmont among them.
Search results carry a brand field, so filtering to one brand is a one-line operation.
Can I track Accor prices over time?
Yes.
The price calendar endpoint returns per-date rates and availability for ranges up to 60 days, and calling it on a schedule builds a rate history.
Sold-out dates arrive as explicit UNAVAILABLE statuses.
How do I find an Accor hotel ID?
Two ways: search by location and read the id field from the results, or paste the property's page URL into the URL-to-ID endpoint.
IDs are short codes like 2185, stable per property.
Ready to simplify your hotel data?
Join other developers using StayAPI to build the next generation of travel applications. Get started for free today.