Inbound Webhooks

What an Inbound Webhook Is

An inbound webhook is the public endpoint a traffic source posts a
lead into. Every webhook has a vanity_uri, a short slug owned by
the company, and is reached at one of two routes:

• POST /api/v1/inbound_webhooks/ping/:vanity_uri
• POST /api/v1/inbound_webhooks/post/:vanity_uri

The first half of the route, ping or post, controls whether the
lead is being shopped to buyers for bids (ping) or being committed
and dispatched to a winning buyer (post). A webhook configured for
simple postback use (no ping/post bidding) only needs the post
route.

How Posted Data is Mapped

Each webhook owns a parser configuration that maps incoming form
fields, JSON keys, or query string parameters onto Trackdrive lead
attributes. The parser fields are managed in the webhook edit
screen and rendered through the same Handlebars form templates the
outgoing webhooks use, so the language you see in the UI ("Extract
Value From Response Body", "Check If Response/Extracted Value
Contains") is the same on both sides.

Where to Find Inbound Webhooks in the UI

Inbound webhooks are managed under the offer they belong to. Open
the offer, then look for the inbound webhook section to add or
edit one. The vanity_uri and any auth requirements are set
there.