Meetings and Events HUB Funnel

The Funnel product (funnel 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 search surface is published separately as Meetings and Events HUB Search.

What it exposes

Clients call the product under the basePath /api/hub/<label>/booking 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 …/booking/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.
  • Booking — POST /booking/create, GET /booking/{tarsId}, GET /booking/user/{pmId}, and the room-level equivalents (/booking-room/create, /booking-room/{tarsId}, /booking-room/user/{pmId}).
  • RFP — request-for-proposal reads and creation (POST /rfps, GET /rfp/{rfpId}, /rfp/parent/{rfpParentId}, /rfp/user, and the /rfps/** equivalents).
  • ACRS — POST /acrs/groups/search, GET /acrs/retrieveGroups/{groupCfNumber}.
  • Distribution — POST /distribution/booking/update, POST /distribution/rfp/update.

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 401; an unknown channel is rejected with 401.