“Personal recommendations on your website and app. +220% revenue per buyer.” — futuredemand.comAffinity is its own product with its own host, its own credential, and its own OpenAPI spec. It is not part of Lookout or Wave and not reached via the Client API.
| Affinity | |
|---|---|
| Host (staging) | https://fd-recommender.stg.future-demand.com |
| Host (production) | https://fd-recommender.prd.future-demand.com |
| Live API reference | /docs (Swagger UI, gated) |
| Credential | Separate from the Client API — request via support.future-demand.com. |
What you can build with it
“Recommended for you” shelf
Personalised recommendations on a logged-in user’s homepage or
dashboard. Pass the user’s identifier, get back a ranked list of
events / products to render.
“You might also like”
Related-item recommendations on an event or product detail page.
Pass the current item id (and optionally the viewer), get back items
likely to interest the same audience.
Personalised landing pages
Render different hero events per visitor based on Affinity’s ranking.
Especially useful for first-time visitors with little site history but
known external signals.
Email and CRM recommendations
Pull a per-recipient recommendation set when composing a marketing
email or CRM workflow. Same call shape as on-page recommendations.
How it fits with the rest of the platform
Affinity sits alongside Lookout and Wave but does not share state with them at the API level. Your integration with Affinity is independent of any Lookout or Wave integration — you can ship Affinity on its own, or alongside one of them.What you’ll do to integrate
Get credentials
Request access at support.future-demand.com.
You’ll receive a token bound to your partner and the requested
environment. See Authentication.
Open the live Swagger UI
The canonical endpoint list lives at
fd-recommender.{env}.future-demand.com/docs.
Browse it once you have a credential — that’s where the request /
response shapes are documented.Try a single call
Follow the quickstart to make one
authenticated request and confirm everything’s wired up.
What this developer kit covers
Until the OpenAPI spec is reachable without authentication, this section of the developer kit covers the integration setup — host, credential, security pattern, error model. The specific endpoints, payloads, and parameters live in the gated Swagger UI at/docs.
Once the spec is exportable (or served unauthenticated), it’ll appear as
a third API Reference tab here.