Create lead by click ID (POST)
Creates a lead using an existing click ID via POST. Alias: /api/v2/network/leads-by-click-id.
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
Affiliate click ID.
Click UUID.
Revenue amount for this conversion.
Affiliate payout amount.
Sale amount.
pending, approved, rejected, hold Advertiser order identifier.
Advertiser user identifier.
Advertiser tracking ID.
Lead email address.
Lead first name.
Lead last name.
Lead phone number.
Lead gender: m=male, f=female.
m, f Lead date of birth (YYYY-MM-DD).
Lead street address.
Lead city.
Lead region/state.
Lead postal/ZIP code.
Lead country code.
Industry vertical identifier.
Visitor IP address.
iOS advertising identifier.
Google advertising identifier.
Deep link URL.
Affiliate sub ID 1.
Affiliate sub ID 2.
Affiliate sub ID 3.
Affiliate sub ID 4.
Affiliate sub ID 5.
Custom affiliate parameter 1.
Custom affiliate parameter 2.
Custom affiliate parameter 3.
Custom affiliate parameter 4.
Custom affiliate parameter 5.
Custom advertiser parameter 1.
Custom advertiser parameter 2.
Custom advertiser parameter 3.
Custom advertiser parameter 4.
Custom advertiser parameter 5.
Custom data field 1.
Custom data field 2.
Custom data field 3.
Custom data field 4.
Custom data field 5.
Custom data field 6.
Custom data field 7.
Custom data field 8.
Custom data field 9.
Custom data field 10.
Note visible to the affiliate.
Internal note, not visible to the affiliate.
Forwards the created lead to the external systems configured for its goal. With yes the lead is posted out; with no (the default) it is only recorded in Scaleo. Delivery needs the Leads Management Module, an active Receive campaign bound to the lead's goal_id, and at least one active Deliver vendor on that campaign - without them, or when a vendor's posting instructions are empty, yes has no effect. Each vendor is called with its own posting instructions (URL, method, headers, tokenized body); its answer is matched against the vendor's success reply and sets the lead's delivery status - success, fail, or empty when the vendor has no success reply configured. Every attempt is stored in the leads log as an Outgoing Lead record. Leads that end up in the trash conversion status (failed campaign validation, geo check, or cap) are never delivered. If the vendor has "return reply" enabled, its raw response is added to the response payload as delivery_reply.
yes, no Conversion timestamp (YYYY-MM-DD HH:MM:SS).
Currency code.
Promo code used by the lead.
Click referrer URL.
Conversion referrer URL.