What you can build
Lookout
Surface event-level demand insights and recommendations to your users:
which events to focus on, expected demand curves, simulation of pricing
or marketing actions, and a portfolio dashboard.
Wave
Build, launch, and measure activation campaigns: package builder for
audience selection, campaign lifecycle, attribution reporting, and
messages.
Affinity
Our recommendation API powering both products — request product or
event affinities for any audience or context.
API Reference
The full OpenAPI surface, kept in sync with production. Use it as a
canonical reference once you understand the call chains.
Where to start
Read the platform model
The Platform Model explains the partner →
client → event hierarchy. Every API call lives somewhere in this tree;
once it clicks, the rest of the API makes immediate sense.
Run the quickstart
Quickstart gets you authenticated and making your first
real call in under 10 minutes.
Lift the TypeScript client
The TypeScript Client is a thin, generated
wrapper around the OpenAPI spec. Drop it into your project to skip the
boilerplate.
How this documentation is organised
- Getting Started — auth, environments, your first call.
- Core Concepts — the mental model behind the API. Read this once.
- Integration Guides — one page per feature, mirroring the screens in the reference Future Demand webapp. This is where the value is.
- Cookbook — recipes for cross-cutting concerns: pagination, polling, uploads, errors, rate limits.
- SDK & Snippets — TypeScript client and React hooks you can use directly.
- API Reference — auto-generated from the OpenAPI spec.
Conventions
Product names are capitalised: Lookout, Wave, Backhaul,
Sentinel, and the recommendation API Affinity. We refer to the whole
platform as Future Demand.
- Base URL:
https://client-api.prd.future-demand.com/api/v3(production) — see Environments. - Auth via API key in the
apikeyheader — see Authentication. - Responses are JSON unless otherwise noted; timestamps are ISO 8601 UTC.
Getting help
- Integration support: support.future-demand.com
- Status page: status.future-demand.com
- Bugs / feature requests: include the request ID from the
x-request-idresponse header so we can trace the call.