Skip to main content
A signal is a named targeting segment — an audience, contextual cohort, or first-party data slice — registered against a storefront and surfaced to buyers for use on campaigns. You register first-party signals directly, discover external segments from signals agents (LiveRamp, Optable, custom) via AdCP, and manage visibility and pricing through access records. Signal endpoints are mounted on the storefront router because signals are owned by the agent/advertiser that registers them, even though buyers consume them on campaigns. Base URL https://api.interchange.io/api/v2/storefront Auth Authorization: Bearer $SCOPE3_API_KEY

​
Task reference

Create signal

POST /signals — register a signal

List signals

GET /signals — filterable, paginated

Get signal

GET /signals/:id — one signal with access records

Update signal

PUT /signals/:id — metadata and access changes

Delete signal

DELETE /signals/:id — archive a signal

Discover signals

POST /signals/discover — query signals agents

Manage ad-server signal components

GET/POST /esa/:id/signals — components backed by ad-server targeting

Signal overview

Fields, lifecycle, sources, and pricing

Errors

Error contract for every operation