Submit a lead

Step 2 of 2 for submitting a lead. Send the same lead_submission you sent to POST /api/v3/partners/{partner_id}/lead_forms/authenticity_token, unchanged, and the token it returned in authenticity_tok. The lead is saved against the partner's live listing and delivered like a lead submitted on the marketplace (notification emails, webhooks and CRM sync configured for the lead form). Always include answers for the form's first name, last name, email and company name fields.

The HTTP status is always 201; read the body to know the outcome. json.success is "true" when the submission was accepted. json.error is Invalid when the answers do not match the token, or Duplicate when a lead with the same email address was submitted through this listing's lead form in the last month; in both cases status is 422 and no lead is saved. A lead that fails validation (a required answer left empty, or an invalid email address or website) is not saved either, but the response still reports success, so validate the answers against the form's fields before you submit.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

Listing ID or slug.

Body Params

Submit a lead

string
required

The token returned in json.encrypted_data by the token step.

lead_submission
object
required

The lead's answers, exactly as sent to the token step: a JSON object that maps each lead form field ID to the answer.

Responses

Language
Credentials
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json