How to use
Authentication
Every call needs the API key of an application subscribed to the product, sent in the apikey header.
curl -X POST "https://rec-api.accor.com/bff/meeting-and-events/v1/graphql" \
-H "apikey: $API_KEY" \
-H "Content-Type: application/json" \
-H "x-target-env: uat1" \
-H "Accept-Language: en" \
-d '{"query":"{ __typename }"}'Headers
| Header | Required | Description |
|---|---|---|
apikey |
yes | API key of the consumer application. |
x-target-env |
no | Sub-environment of the BFF. REC: dev1, uat1 (default), devds. PREPROD: preproduction (default), preproduction2. Ignored in PROD. |
Accept-Language |
no | Locale of the response: en, fr, de, es, it, pl, pt (fr by default). |
A missing or unknown x-target-env value is routed to the default sub-environment.
Gateways
| Environment | Gateway |
|---|---|
| REC | https://rec-api.accor.com |
| PREPROD | https://pre-api.accor.com |
| PROD | https://api.accor.com |
Errors
Errors produced by the gateway follow the platform format: {status, title, code, detail, requestId}.
Quote the requestId when contacting the support.