Skip to main content
POST
cURL

Overview

The Source Form API is the primary lead submission endpoint for a specific campaign source. It accepts a full lead record from a publisher or media partner and routes it through the campaign’s distribution logic. This endpoint is equivalent to the Create Form API but is scoped to a source identified by its unique link ID rather than a campaign ID. It is the endpoint listed in your posting specification under “Form API”.

Endpoint

Replace {source-unique-id} with the linkUniqueId provided in your posting specification. This value is unique per source-campaign pairing.

Authentication

Include the source API token in the Authorization header:
The token is listed in your posting specification under the Form API section.

Request Parameters

Path Parameters

Body Parameters (JSON or form-encoded)

Campaign-specific custom fields (e.g. loan_amount, home_owner, insurance_type) may also be required. Your posting specification lists all active fields with their required status.

Example Request

Example Responses

Success — Lead Accepted (Sold)

Success — Lead Unsold

Error — Invalid Field

Status Codes

Tips

  • Check your posting spec: The exact list of required and optional fields, acceptable values, and field descriptions are auto-generated in your campaign’s posting specification page.
  • Mobile number format: Send only digits. The API strips non-digit characters, but a 10-digit number is required (e.g. 4085559876 not +1 (408) 555-9876).
  • Custom transaction IDs: If you supply a transaction_id, it must be unique per lead. Reusing an ID may overwrite or conflict with existing records.
  • Redirect handling: Store the redirect_url from the response and immediately redirect the consumer to it for optimal conversion.
  • ZIP code lookup: The API can resolve city and state from zip_code if those fields are not submitted, depending on campaign configuration.