> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.westiq.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.westiq.ai/_mcp/server.

# FAQ

#### How do I get access to these docs?

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.

#### How do I get API credentials?

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.

#### Is the sandbox catalog real airline content?

No. West loads the sandbox with a demonstration catalog so you can
integrate against the real authentication, tenancy, search, and events
surface without your airline's catalog. Loading a real airline catalog
is part of production onboarding.

#### Where is the full API reference?

In the [API Reference](/api-reference) section — generated from the
platform's OpenAPI document. The live API serves the same document at
`GET /openapi/v1.json`.

#### Why am I getting 400 session.unresolved?

The per-member personalization, shopping, ads, and destination endpoints (see the full list
on [Sessions & Member Locators](/guides/sessions#the-x-session-id-header)) 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.

#### Who do I contact for support?

Email [partners@westiq.ai](mailto: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.