WestIQ Partner Documentation
Welcome to the WestIQ partner documentation. These docs are public; API access is credential-gated — partner credentials are issued during onboarding.
WestIQ delivers AI-driven personalization for in-flight entertainment. This site documents the WestIQ Platform API (v1) — the server-to-server integration surface of the WestIQ platform.
What you can do today
Authentication is OAuth 2.0 client credentials. Your credential is bound to your airline on the WestIQ side — you never send an airline identifier, and your calls can only ever see your airline’s catalog plus the shared global catalog. The per-member endpoints additionally use a passenger-session locator — see Sessions & Member Locators.
Access is granted to approved airline and integration partners. Need access or API credentials? Contact your WestIQ partner manager.
Where to start
- Quickstart — get a token and make your first authenticated call.
- Authentication & Access — the credential model, the one scope, and the auth failures you can hit.
- Sessions & Member Locators — the
X-Session-Idheader, seat/member locators, and the age-tier model the per-member endpoints share. - Search — how queries are parsed, scored, and how catalog coverage is reported.
- Behavioral events — batching passenger interaction signals, rejection codes, and the signal vocabulary.
- Personalization — theme, session setup, personas, catalog serve, suggestions, enrichment, and session events.
- Catalog operations — catalog ingestion (submit your titles in batches and poll the job), product ingestion (the same flow for duty-free, food & beverage, and retail products), and flights & active catalog (register a flight, then push the titles actually loaded on the aircraft).
- Shopping & ads — shopping search, shopping curate & rescore, and ads decisioning.
- Destination — search & replace, plan & extend, weather, and the shared hero images endpoints.
- Errors & limits — the error envelope, correlation IDs, request limits, and rate limiting.
- API Reference — the full endpoint reference, generated from the platform’s OpenAPI document.
- Security & Trust — isolation, encryption, PII handling, and our compliance posture, stated as proofs rather than promises.