Skip to main content

Overview

Audience results are read from runs. A run can be manual, daily, or preview; public run creation supports manual runs. Daily refreshes are scheduled for eligible active audiences.

Queue a manual run

Use Idempotency-Key when retrying from a client. The key can be up to 120 characters. Reuse it for retries of the same intended run; choose a new key for a new run. An existing in-flight run may also be returned instead of creating a duplicate. The audience must be active before you queue a run. A successful queue response is 202, not confirmation that contacts are ready.

Response

List runs

Cancel a queued run

Only queued runs can be cancelled. Completed, failed, running, or already cancelled runs cannot be cancelled.

Run status values

Notes

  • Each run is a separate snapshot.
  • Use the run ID for results, stats, and exports.
  • Result endpoints return 202 while a run is queued or running.
  • Request only manual runs through the public run-creation API; daily refreshes are scheduled automatically.
  • Pausing stops future automatic refreshes. Read dailyRefreshEnabled and account access instead of assuming every active audience has the same refresh entitlement.

Next steps

  • Read Get people to retrieve hydrated results from a completed run.
  • Read Stats and export to inspect fill rates or download CSV data.