Webhooks

Segment build succeeded

POSTed to your webhook URL when an async segment (matched file upload, similarity, or propensity) completes successfully. Configure your URL via PUT /v1/settings/webhook, supply webhook_url per-request, or subscribe via POST /v1/webhook-subscriptions. subject.id is the segment id; data.audience_id is also present when an audience wrapper was auto-created alongside the segment (create_audience: true, which is the default for matched segments). See the Webhooks tag for the envelope shape and signing scheme.

postWebhooksegment.ready

Payload

idstring required

Unique per event firing — stable across retries of the same delivery.

type'segment.ready' required

created_atstring date-time required

api_versionstring required

org_idstring required

linksobject required

Reserved for future related-resource links. Currently always empty.

Example payload

{
  "id": "evt_1a2b3c4d5e6f7a8b9c0d1e2f",
  "api_version": "2026-08-06"
}

Response

Your endpoint acknowledged the event.

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.