Hotel brand and destination research
Use Accor endpoints to turn hotel brand and destination research into repeatable API requests with documented inputs and JSON responses.
Turn Accor's public hotel index into structured JSON — typeahead and paginated search across the group's properties, destination and brand directories, a geographic catalog lookup, an amenity reference catalog, and static per-property metadata including brand, city/country, amenities, and published check-in/check-out times. Credential-free, and deliberately scoped to static public data: no booking, rates, rooms, or review text.
Search Accor's public hotel index, walk destination and brand directories, and resolve a hotel code to static property metadata — all as structured JSON.
Endpoint families
6
Documented params
32
Examples
8
Live catalog snapshot
Active endpoints
8
Methods
GET
Required params
14
Schema refs
8
{
"platform": "Accor",
"endpoint": "accor-search",
"method": "GET",
"path": "/accor/search",
"auth": "apiKey"
}Use cases
Search Accor's public hotel index, walk destination and brand directories, and resolve a hotel code to static property metadata — all as structured JSON.
Use Accor endpoints to turn hotel brand and destination research into repeatable API requests with documented inputs and JSON responses.
Use Accor endpoints to turn competitive property and amenity mapping into repeatable API requests with documented inputs and JSON responses.
Use Accor endpoints to turn travel content aggregation into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Accor endpoint catalog — 8 endpoints, 32 documented request parameters, and 8 published response schemas — the same catalog Docs and Playground run against.
8 documented Accor endpoints, grouped into 6 request families — Search, Amenities and Brands, plus 3 more.
32 request parameters are documented across those Accor endpoints, 14 of them required — the full input contract is public before you write any integration code.
8 of the 8 Accor endpoints ship a recorded example response, and 8 carry a documented response schema — you can code against the real JSON before the first request.
Accor endpoints document their error responses (400, 429, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
8 hosted MCP tools back the Accor endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/accor/search
/accor/amenities
/accor/brands
/accor/catalog/hotels
/accor/destination/hotels
/accor/property
Endpoint catalog
/accor/searchSearches the public Accor hotel index by destination or hotel name, with optional country, city, brand, star, page, and page-size filters. Results contain static hotel identity, location labels, ratings, and source URLs; booking, rates, rooms, reviews, loyalty, and payment flows are excluded.
MCP tool accor_search
/accor/search/suggestReturns anonymous Accor typeahead suggestions for a partial destination or hotel query, including destination/place and hotel identifiers, types, labels, and match metadata. It uses the public search-box suggestion source only; booking, rates, rooms, reviews, and result-list requests are excluded.
MCP tool accor_search_suggest
/accor/search/detailsResolves an anonymous Accor search suggestion identifier to its description, coordinates, viewport, radius, and address components. It uses the same public place-details source as the Accor search box; booking, rates, rooms, reviews, and account data are excluded.
MCP tool accor_search_details
/accor/catalog/hotelsSearches Accor's anonymous public hotel catalog by text, hotel code, or latitude/longitude radius. Results contain static property identity and broad location metadata plus catalog relevance/distance; contact details, precise hotel coordinates, payment, loyalty, media, rates, rooms, reviews, and booking data are excluded.
MCP tool accor_catalog_hotels
/accor/destination/hotelsReturns the static list of hotels published on one Accor destination directory page (world, continent, country, region, department, city, district, or place), optionally narrowed by a theme facet. Each hotel carries its code, name, source URL, and broad city/country. Booking, rates, rooms, reviews, contacts, and precise location are excluded.
MCP tool accor_destination_hotels
/accor/propertyReturns static public metadata for one Accor hotel code, including name, brand, city/country, explicitly listed amenities, and published check-in/check-out times. Booking, rates, rooms, reviews, contacts, and precise location are excluded.
MCP tool accor_property
/accor/brandsReturns the Accor brand directory published on the public brands page, with each brand's name, slug, and source URL. Booking, rates, rooms, reviews, contacts, and location are excluded.
MCP tool accor_brands
/accor/amenitiesReturns the anonymous public Accor amenity catalog with stable amenity codes, labels, categories, and display ordering. It is reference data for interpreting hotel search facets; booking, rates, rooms, reviews, and account data are excluded.
MCP tool accor_amenities
Related APIs
Travel & Hospitality
Build travel and lodging research workflows from structured Airbnb stay, room, availability, and review data.
Travel & Hospitality
Research hotels, restaurants, attractions, and destination pages from TripAdvisor with normalized listing and review endpoints.
Travel & Hospitality
Turn Expedia's Stays, Flights, and Things To Do results into structured JSON — destination search, hotel listings with pricing and reviews, flight offers, and activity search, sourced from the same API the official mobile app uses. Credential-free.
How to scrape Accor
Crawlora covers Accor's public hotel index in eight endpoints — typeahead, search, place details, a geographic catalog, destination and brand directories, an amenity reference catalog, and per-property metadata — all normalized JSON behind one API key, with no account or signed session.
Send a partial query to /accor/search/suggest for Accor's own typeahead. Suggestions come back tagged with a source of google_places or hod_hotels plus an id, which /accor/search/details turns into coordinates, a viewport, a radius, and address components.
Call /accor/search with a destination or hotel name, optionally narrowed by country, city, brand or stars. Results are paginated (the response reports total and pages) and each hotel carries its hotel_code, name, brand and brand_label, city/country, star rating, aggregate rating and review count, and canonical source URL.
/accor/destination/hotels lists the hotels Accor publishes on one destination page — pass a destination_type of world, continent, country, region, department, city, district or place, plus that page's slug (the full form, e.g. hotels-dusseldorf-v1158, not just the city name). /accor/brands returns the group's full brand directory in one call.
/accor/catalog/hotels searches the anonymous public catalog by text, hotel code, or a latitude/longitude radius in kilometres, with offset/limit paging. Each hit carries the property's identity, chain, lodging type and open/closed status — useful for mapping a group's footprint around a point.
Pass a hotel code to /accor/property for the property's name, brand, city/country, explicitly listed amenities, and published check-in/check-out times. /accor/amenities returns the reference catalog behind those amenity codes — stable codes, labels, categories, and display ordering — so you can decode and group them consistently.
FAQ
Search for it. /accor/search takes a destination or hotel name and returns each matching property with its hotel_code, and /accor/search/suggest gives you Accor's typeahead if you only have a partial destination. You can also read codes off a destination directory page via /accor/destination/hotels, or out of a hotel's canonical URL, which has the form all.accor.com/hotel/{code}/index.en.shtml.
No. Every Accor endpoint is scoped to static public data — booking, rates, rooms, review text, contact details and precise hotel coordinates are all excluded by design. Search results do include a property's aggregate star rating and review count, but not the reviews themselves.
The theme facet on /accor/destination/hotels — 4-stars, luxury, pet-friendly, spa and the rest — mirrors the themed pages Accor actually publishes for that destination. If Accor has no themed page for that combination the request 404s rather than returning an empty list, so treat a 404 there as "this facet does not exist for this destination", not as an error in your call.
/accor/search is the public site search — text-driven, paginated, and returns the presentation-layer fields a visitor sees, including stars and aggregate rating. /accor/catalog/hotels is the underlying catalog lookup: it accepts a hotel code or a latitude/longitude radius as well as text, uses offset/limit paging, and returns identity and operational fields such as chain, lodging type and open/closed status. Use search for discovery, the catalog for geographic sweeps and code resolution.
Collecting publicly accessible hotel metadata is generally permissible if you respect Accor's terms of use, robots directives, rate limits, and applicable law. This is for public data you are authorized to collect — and the endpoints are deliberately limited to the static, anonymous surface rather than anything behind a booking session or loyalty account.