Skip to main content
POST /api/v2/storefront/signals Registers a signal so it can be deployed and surfaced to buyers. You set the key types at creation, and keyType is immutable afterward. countries lists the ISO 3166-1 alpha-2 countries where the signal may be used, as in AdCP’s SignalDefinition; leave it out for no restriction, and change it later with Update signal. Use access records to control visibility (PUBLIC or PROPRIETARY) and optional per-advertiser pricing.

Request

Parameters

Response

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; a countries entry that is not an assigned ISO 3166-1 alpha-2 code; a regions field (replaced by countries); a price that is not an AdCP VendorPricingOption; 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