Create lead upon delivery (POST)
Creates a lead with deferred delivery via POST.
Authorizations
Preferred authentication method. Pass the API key in the X-API-Key HTTP request header. The user account must have api_status enabled.
Body
Not evaluated on this endpoint - deferred delivery is what it does. When the goal has an active Receive campaign with at least one active Deliver vendor, every such vendor is called before the lead is stored, and each attempt is written to the leads log as an Outgoing Lead record. The verdict comes from the last vendor in that loop: only if its answer matches its configured success reply is the lead recorded and 200 returned. Otherwise the endpoint returns 400 The Lead creation failed and no conversion is stored - but the outgoing requests have normally already gone out, so retrying the call re-sends the lead to every vendor that already accepted it. A vendor with no success reply configured never matches, so a campaign whose last vendor is in that state answers 400 for every lead it has in fact delivered. When the goal has no such campaign or vendor, or the lead ends up in the trash conversion status, no delivery is attempted at all: the lead is recorded and the endpoint answers 200.
yes, no