t
TasteOS
/api/public/v1
Bridges

Attune Exposure Bridge

Reference Attune exposure IDs on signals and outcomes — what the user actually saw, when, and in what moment context.

How it works

TasteOS does not duplicate Attune's exposure ledger. Instead, every signal and outcome can store an attune_exposure_id that points back to the canonical moment record in Attune.

Attune answers: "what to show, suppress, prioritize, defer, or ask next right now."

TasteOS uses Attune's exposure context to interpret signals (click, save, reject, never_show_again, more_like_this, correction) and to attribute outcomes (conversion, completion).

Signal payload pattern

POST /api/public/v1/taste/signals
{
  "taste_profile_id": "…",
  "source_product": "next_up",
  "action": "saved",
  "signal_type": "implicit_behavior",
  "preference_direction": "positive",
  "intent_strength": "strong",
  "attune_exposure_id": "exp_2026_…",
  "option_id": "…"
}