FAQ

The documentation is public — you are reading it. Access to the API itself is credential-gated: contact your WestIQ partner manager for your API credential.

Your OAuth 2.0 client_id and client_secret are issued during partner onboarding, together with your token endpoint URL. The credential is issued already bound to your airline — you never send an airline identifier on any request. Credentials are separate from docs access.

No. The sandbox runs a fully synthetic demo-airline catalog so you can integrate against the real authentication, tenancy, search, and events surface without touching licensed content. Loading a real airline catalog is part of production onboarding — the end-to-end integration walkthrough in your partner onboarding pack covers it.

In the API Reference section — generated from the platform’s OpenAPI document. The live API serves the same document at GET /openapi/v1.json.

The per-member personalization, shopping, ads, and destination endpoints (see the full list on Sessions & Member Locators) require an X-Session-Id header, and the SSE routes require a session id in the path. A missing or invalid value fails closed with 400 session.unresolved. A handful of model-free endpoints (theme, the unscored catalog read, hero images, destination weather) don’t need it at all.

Email partners@westiq.ai or your partner manager. Include the X-Correlation-Id response header value from any failing request — it is how we find your request in our logs.