Refresh a member segment and this audience's composed metadata
Re-derives one member segment of this audience from the latest identity graph data, then bumps only this audience's own composed metadata (snapshot_version/expires_at/status; record_count is cleared and must be re-requested via POST /v1/audiences/{id}/count). An audience is a composition of N member segments (possibly mixed subtypes) — there is no "primary" segment. You must name exactly which member segment to refresh via the required segment_id body field (list an audience's segments via GET /v1/audiences/{id}). That segment's refresh delegates entirely to the same implementation POST /v1/segments/{id}/refresh uses, so behavior for the named segment is identical either way. This route never touches any OTHER segment in the composition, and — since segment refresh is deliberately non-cascading — never touches any OTHER audience that happens to reference the same segment. Behavior is driven by the refreshed segment's subtype:
filter — Synchronous refresh. The audience is immediately returned as status: active with an incremented version number and a new 90-day expires_at. The record_count is cleared and must be re-requested via POST /v1/audiences/{id}/count.
matched — Returns a fresh presigned upload_url (24 h expiry) — or upload_urls (an array, one per shard) when shard_count > 1, in which case upload_url is absent. The new upload may be raw or gzip. With hitl unset/false (default): returns status: pending immediately and the URL(s) target the canonical upload path — re-upload your identity list and identity resolution runs automatically once every declared shard has been uploaded. With hitl: true: the segment's status is left untouched and the URL(s) instead target a staging location — call POST /v1/match/{segment_id}/analyze to preview column mappings, then POST /v1/audiences/{id}/mappings to confirm (starts resolution) or POST /v1/audiences/{id}/mappings/cancel to abort.
similarity/propensity — Re-launches the generation workflow. Returns status: pending plus a workflow_run_id; poll GET /v1/workflows/{workflow_run_id} until completion.
Important: Delivery requests are rejected with 422 while constituent segments are still being processed.
To refresh a single segment without touching its audience wrappers, use POST /v1/segments/{id}/refresh — it updates only that segment and returns affected_audiences for follow-up. Requires 'creator' scope.
Request
- Base URL: https://api.infiniteaudience.ai
- URL: https://api.infiniteaudience.ai/v1/audiences/{id}/refresh
- Auth: HTTP bearer
Path parameters
Audience document ID.
Request body
Response
Audience refreshed. Inspect status to determine next steps. See next_step for a machine-readable hint.
Changes
No recorded changes to this operation across all 1 revision of this API.