Meetings and Events HUB Search

The Search product (server app) of the Meetings & Events HUB, the middleware consumed by the M&E back ends. It is one of the two products migrated from the shared Apigee proxy to Accor's APIM gateway; the booking funnel is published separately as Meetings and Events HUB Funnel.

What it exposes

Clients call the product under the basePath /api/hub/<label>/search on the gateway host of the target environment. Each environment has its own fixed label, the one already used before the migration, so current URLs keep working:

The surface is:

• GraphQL — POST …/search/graphql, the main query/mutation endpoint called server to server by the back ends that consume the M&E HUB.
• REST:
  • Service — GET …/healthcheck, GET …/version.
  • Property — list and search (/property/list, POST /property/search/bestoffers) plus per-property detail and sub-resources (/property/{id} and its amenities, facilities, media-details, reviews, and the meeting-rooms, options, rooms POST operations).
  • Referentials — reference data under /referentials/** (brands, countries, currencies, civilities, amenities, meal-plans, snacks, drinks, payment-means, meeting-room-amenities, phone-validate, and the accommodation/{assets,beddings,extras,views} sets).
  • Webhooks — POST /webhooks/meeting-package/property/created and POST /webhooks/property-referential-app/property/upserted.

Only these declared paths are routed; any undeclared path returns 404.

Authentication

Unchanged by the migration. Send your existing apikey in the apikey or x-api-key header. One application key works across both Meetings & Events products — no re-subscription is required.

Required headers

channelid identifies the calling channel. A request without it is rejected with 400; an unknown channel is rejected with 401.