Prospect Webhooks | Audienti

Purpose

Prospect webhooks are for systems that already know which list a prospect should enter and can send one normalized prospect per request.

Prerequisites

A target list with a clear owner.
A user API token belonging to someone who can access the account.
A sending system that can post one normalized prospect per request.

Steps

Create a dedicated endpoint for each target list rather than sharing one generic URL.
Validate the payload shape against the accepted field list before going live.
Send a test delivery and confirm the target list receives the prospect.
Watch recent deliveries after launch to catch schema or auth failures early.

Verification

Inbound webhook endpoint showing status, target list, URL, and recent deliveries — Check endpoint status, target list, and recent deliveries before relying on the webhook.

Common mistakes

Using a webhook before the receiving list has an owner.
Sharing one endpoint across different sources and then losing provenance.
Skipping recent-delivery review after launch.

A webhook is only useful if the receiving list and follow-up workflow are already defined. Set that up first in your workspace guide.