How to use

Base URL

Call the product under /api/hub/<label>/booking on the gateway host of the target environment. The label is fixed per environment and unchanged by the migration: dev (dev), sandbox-2 (rec), oat (preprod), pro (prod) — for example /api/hub/pro/booking in production. GraphQL is at …/booking/graphql; REST operations sit directly under the basePath, for example GET …/booking/healthcheck or GET …/booking/{tarsId}.

Required headers

• apikey (or x-api-key) — your existing application key, on every operation. It is unchanged by the migration and one application key works across both Meetings & Events products — no re-subscription is required.
• channelid — the identifier of your calling channel, on every operation except healthcheck and version (GraphQL included). Missing: 401; unknown channel: 401.

POST /api/hub/pro/booking/graphql
apikey: <your-api-key>
channelid: <your-channel-id>
Content-Type: application/json

Notes

• Only the declared paths (listed in the description) are routed; any other path returns a 404 with the standard not-found body.
• Dev only: the optional x-target-env header selects the backend sub-environment (dev, qa, sandbox, uat); absent or unknown, dev is used.