Leads Capture API

Endpoint

POST /api/v1/leads/capture is the primary entry point
for pushing a lead into TrackDrive from an external CRM,
landing page, or marketing automation system without going
through the inbound webhook parser layer. The payload is
JSON or form-encoded.

Required Fields

At minimum the request must include the company access
token (header or auth_token) and enough identifying
fields to construct a lead: typically a phone number, an
offer identifier, and any custom fields the offer expects.

Response

A successful capture returns the created lead's ID and any
schedule it was attached to. If the lead matched an
existing record on phone number, the response indicates
the dedupe action taken.

Why Use Capture Over Inbound Webhook

The inbound webhook route exists to let traffic sources
hit a vanity URL with whatever shape of payload they
happen to send, and rely on the parser to translate it.
The capture endpoint is the inverse: it requires the
caller to send a well-formed TrackDrive payload and
bypasses parsing entirely. Use capture when the
integration is yours to design; use inbound webhooks when
the traffic source dictates the shape.