Reports conversions

Seed example (keychains curl)

I’m ready to generate the exact keychains curl command, but I’m not seeing a documented Booking.com Demand API endpoint at /reports/conversions in the current public docs. Here’s what I found and how I can proceed:

What I found
- Booking.com Demand API (v3.2) base URL for production is https://demandapi.booking.com/3.2/ (sandbox at https://demandapi-sandbox.booking.com/3.2/). The API is REST/JSON and uses Bearer token authentication with an affiliate ID header in some calls. The documented endpoint groups include Accommodations, Cars, Common/Locations, Languages, Languages, and Orders; there is no public /reports/conversions endpoint listed in the v3.2 reference. ([developers.booking.com](https://developers.booking.com/demand/docs/open-api/3.2/demand-api))
- The OpenAPI spec for Demand API (3.2) confirms the same production/sandbox hosts and endpoint structure, with /accommodations, /cars, /common, /orders, etc., but again no /reports/conversions endpoint is shown in the documented paths. ([developers.booking.com](https://developers.booking.com/demand/docs/open-api/3.2/demand-api))
- Separately, Booking.com’s Metasearch Connect API does expose a /reports/conversions endpoint (under the “reports” collection) with a production URL like https://metasearch-connect-api.booking.com/reports/conversions and a POST that returns conversions data. This is a different API product (Connect/Metasearch), not the Demand API. ([developers.booking.com](https://developers.booking.com/metasearch/connect-api/open-api/reports?utm_source=openai))

What I can do next
- If you indeed want to use Booking.com Demand API, I can generate a curl for a documented endpoint (e.g., /orders/create or /orders/preview) using the standard placeholder pattern, once you confirm the exact endpoint you intend to call. The required placeholders would be {{OAUTH2_ACCESS_TOKEN}} for the token and {{BOOKING_AFFILIATE_ID}} (or header variant) as appropriate. Example structure would follow the same formatting you provided, but I’ll tailor the body to the endpoint’s schema once you confirm.
- If you meant Booking.com’s Metasearch Connect API (the /reports/conversions endpoint that exists there), I can generate a precise keychains curl for that endpoint right away, using the standard placeholders (e.g., {{$from_date}}, {{$to_date}}, {{$page_size}}) and the same header conventions. Here’s a ready-to-run example for that endpoint (production host):

  npx -y keychains@latest curl "https://metasearch-connect-api.booking.com/reports/conversions" \
    -X POST \
    -H "Content-Type: application/json" \
    -H "Authorization: Bearer {{OAUTH2_ACCESS_TOKEN}}" \
    -d '{"checkout_date_range": {"from": "{{$from_date}}", "to": "{{$to_date}}"}, "page_size": {{$page_size}}, "page_token": "{{$page_token}}"}'

Variables I’d include for the Connect API example:
- from_date: Start date for the checkout window (YYYY-MM-DD)  - example: 2025-01-01
- to_date: End date for the checkout window (YYYY-MM-DD)  - example: 2025-01-31
- page_size: Number of results per page  - example: 100
- page_token: Pagination token (empty string for first page)  - example: ""

If you confirm which API product and endpoint you want (Demand API vs Metasearch Connect), I’ll return a single, exact curl command starting with npx -y keychains@latest curl and a corresponding variables array in the exact format you provided.

Citations:
- Booking.com Demand API docs and base URLs / endpoints (3.2): production URL https://demandapi.booking.com/3.2, sandbox, and the endpoint grouping (Accommodations, Cars, Orders, etc.). ([developers.booking.com](https://developers.booking.com/demand/docs/open-api/3.2/demand-api))
- Demand API 3.2 OpenAPI JSON/YAML reference (available endpoints shown; no /reports/conversions path in the listed paths). ([developers.booking.com](https://developers.booking.com/_spec/demand/docs/open-api/3.2/demand-api.json?download=))
- Booking.com Connect/Metasearch API: /reports/conversions endpoint exists there. ([developers.booking.com](https://developers.booking.com/metasearch/connect-api/open-api/reports?utm_source=openai))