Create signal

POST /api/v2/storefront/signals Registers a signal so it can be deployed and surfaced to buyers. You set the key types and regions at creation; keyType and regions are immutable afterward. Use access records to control visibility (PUBLIC or PROPRIETARY) and optional per-advertiser pricing.

Request

curl -X POST https://api.interchange.io/api/v2/storefront/signals \
  -H "Authorization: Bearer $SCOPE3_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "signalId": "acme_high_value_customers",
    "name": "Acme — High-Value Customers",
    "description": "Top 10% LTV customers, refreshed weekly",
    "keyType": ["rampid", "uid2"],
    "regions": ["NORAM", "EMEA"],
    "isLive": false
  }'

{
  "signalId": "acme_auto_intenders",
  "name": "Acme — Auto Intenders",
  "description": "In-market auto shoppers, last 30 days",
  "keyType": ["maid"],
  "regions": ["NORAM"],
  "access": [
    {
      "advertiserId": 88421,
      "visibility": "PROPRIETARY",
      "price": {
        "pricing_option_id": "po_cpm_standard",
        "pricing_model": "cpm",
        "currency": "USD",
        "fixed_price": 2.5
      }
    }
  ],
  "isLive": true
}

Parameters

Field	Type	Required	Notes
`signalId`	string	Yes	Caller-supplied stable identifier. Pattern `^[\w\-:.]+$`, max 255. Immutable
`name`	string	Yes	Human-readable name (max 255)
`keyType`	string[]	Yes	Identifiers the segment is keyed on. At least one context type (`country`, `region`, `metro`, `topic`, `eidr`, `gracenote`, `isrc`, `gtin`, `rss_guid`, `isbn`, `url`, `url_hash`, `custom`) or identity type (`maid`, `rampid`, `rampid_derived`, `hashed_email`, `hashed_phone`, `id5`, `uid2`, `euid`, `pairid`) — never both classes on one signal. Immutable
`agentId`	string	No	Owning signals agent (for agent-managed signals)
`description`	string	No	What the segment represents (max 5000)
`regions`	string[]	No	Availability regions: `NORAM`, `LATAM`, `EMEA`, `APAC`, `ANZ`, `GLOBAL` (max 6). Immutable
`metadata`	object	No	Free-form key/value metadata
`access`	object[]	No	Access records. Each requires `advertiserId` (int64) and `visibility` (`PUBLIC` or `PROPRIETARY`); optional `price`
`isLive`	boolean	No	Whether the signal is deployed and accepting buys. Default `false`

Response

{
  "signal": {
    "id": 50213,
    "signalId": "acme_high_value_customers",
    "customerId": 1001,
    "adcpAgentId": null,
    "name": "Acme — High-Value Customers",
    "description": "Top 10% LTV customers, refreshed weekly",
    "keyType": ["rampid", "uid2"],
    "regions": ["NORAM", "EMEA"],
    "metadata": null,
    "isLive": false,
    "archivedAt": null,
    "createdBy": "agent@acme.example",
    "updatedBy": null,
    "createdAt": "2026-06-06T12:00:00Z",
    "updatedAt": "2026-06-06T12:00:00Z"
  },
  "access": []
}

The numeric id and the string signalId are both returned. Pass signalId to every sibling operation.

Errors

400 VALIDATION_ERROR — missing signalId, name, or keyType; malformed signalId; an empty keyType array; or a keyType array that mixes context types with identity types (a single signal must be one class or the other — see Key types and the privacy boundary).
401 UNAUTHORIZED — missing or invalid bearer token.

See Errors for the full error contract.

Signal tasks

All signal operations

Signal overview

Fields, lifecycle, and concepts

Update signal

Change metadata and access records

Discover signals

Find external segments from agents

Start building

Core Concepts

Buyer operations

Seller operations

Cross-Cutting Reference

Buyer API reference

Seller API reference

Release Notes

Request

Parameters

Response

Errors

Signal tasks

Signal overview

Update signal

Discover signals

​Request

​Parameters

​Response

​Errors

​Related

Signal tasks

Signal overview

Update signal

Discover signals

Request

Parameters

Response

Errors

Related