Activity & reporting

https://api.interchange.io/api/v2/storefront

​

Key concepts

• Reporting is participation-based. The storefront does not own the underlying media buys. Reporting is visible because the Merchandising Agent is the ADCP party to those transactions. The hierarchy is advertiser → media buy → package — there is no campaign level.
• Two reporting views. summary returns a hierarchical advertiser/media-buy/package breakdown; timeseries returns flat per-day rows. Use inventorySourceId to scope to one source.
• Activity is append-only. The audit feed records configuration and inventory-source changes. Each row attributes the actor (user or service token), records how the action was initiated (actorOrigin: human, agent, autonomous, or system) and whether it took effect (outcome: succeeded, denied, or failed), and carries the before/after changes. The default feed shows succeeded changes; filter outcome=denied or outcome=failed to audit blocked or errored attempts. Connecting a payout account (REGISTER) is included.
• The feed is also in chat. Sellers don’t have to call the endpoint: in the storefront chat, Activity log (or /activity) renders this feed as a read-only panel with actor-origin and outcome chips, and a direct question — “who changed our billing?”, “what changed yesterday?”, “what got blocked?” — is answered in prose from the same data.
• Moderation pre-check never blocks. It returns structured findings so an agent can self-correct. wouldBlock tells you whether the same content would trigger a 422 on a real blocking surface.

​

Task reference

​

Related