Generic POST instructions for LeadConduit

These are instructions for submitting leads into a LeadConduit flow using the default integration  

Posting URL Format

LeadConduit posting URLs have a consistent format. There are two parts of the URL that vary:{{FLOW ID}}/sources/{{SOURCE ID}}/submit

  • Flow ID — The 24 character flow ID generated by LeadConduit that uniquely identifies the flow receiving your lead.
  • Source ID — The 24 character source ID generated by LeadConduit that identifies the source of the lead.  

NOTE: The Flow and Source IDs are very important to ensure the lead goes into the correct flow and is attributed to the correct source. The sample URL above will not work because it contains placeholders for flow ID and source ID.  The actual URL with real Flow and Source IDs must be obtained by the LeadConduit account holder for the appropriate Flow/Source combination. 

Request Method

LeadConduit supports receiving leads using a GET or POST request. We strongly recommend using POST.

Request Headers

The two headers shown below are required when submitting leads using the POST method. The Content-Type header may be omitted for GET requests.

Accept: application/json
Content-Type: application/x-www-form-urlencoded

You may also submit leads using the XML or JSON Content-Type if you use our standard format. Please contact for more information.

Supported Fields

Each flow contains a unique set of acceptable fields. Please check with the administrator of the account to learn more. To view all of the common fields in the generic integration, please view the collection of fields here.

About Data Types

The supported fields table lists each field supported by LeadConduit. Each field has an associated type, which is used to help make sense out of the data you provide.

If a field is provided with a value that cannot be interpreted as the expected type, no error will be given unless the LeadConduit account holder has explicitly configured the flow to do so.

Nevertheless, your leads have the best chance of making it through the system when the data provided in each field is comprehensible to LeadConduit.


Data Type Description Examples


Any string data which can include alphanumeric characters, whitespace, special characters, new lines, etc.

“I would like some information on your product”


Any string which can be parsed to a number


date, dob

Most strings which are reasonably recognizable as a date

“1995-12-25” (recommended)
“Dec 25, 1995”


A US Social Security Number. Data submitted in this field transient. It is never stored or logged by LeadConduit.

“123 45 6789”

postal code

A US, UK, or Canadian postal code

“AA11A 1AA”


A US State abbreviation, or international locality



A numeric range, with a high and low boundary. A non-range is also acceptable provided is a number

“1 to 10”


Gender of the consumer



A US phone number in a common format (optional extension must be preceded by the x character). To specify the type of the phone number append “h” for home, “w” for work, or “m” for mobile to the number.

“512-789-1111 x1234”
“(512) 789-1111h”
“(512) 789-1111w”


An email address


Real-time feedback

When a lead is submitted, LeadConduit provides real-time feedback in the HTTP response body. This feedback identifies which one of three possible outcomes occurred. The outcome is derived from a series of actions and rule evaluations that take place while the lead is processed through the flow. The process of each flow is different because it is based on the individual needs of the LeadConduit account holder.

The possible outcomes are:

  • Success — The lead was accepted by the buyer.
  • Failure — The lead was not accepted by the buyer. The reason field explains why.
  • Error — An unexpected problem occurred and lead handling was unable to proceed normally. The lead was not accepted. The reason field provides more detail. 

Real-time feedback in the response always contains the 24 character LeadConduit lead identifier. If possible, capture this value in your system. It can be used to track down discrepancies or help troubleshoot problems.

HTTP Response Codes

You can expect a HTTP 201 for every correctly handled lead submission. 

It is possible that you may also receive an HTTP 502, 503, or 504 response if the system is under extremely high load. This is a transient condition, and you should retry sending the lead submission request again in a few seconds. 

Any other status code in the 400 or 500 range should be reported to Please be sure to include the full HTTP request information (GET vs. POST, URL, and parameters being sent).

Sample Lead Submissions

The examples in this section show lead submissions from the command line using the ubiquitous curl utility.

The below example shows the successful submission of a lead:

The below example shows the submission of a lead that failed because it was a duplicate:



Was this article helpful?
4 out of 7 found this helpful
Have more questions? Submit a request


You must be logged in to comment.