Skip to main content
POST
cURL

Overview

The Source Post API is the second step in a two-call ping-post flow. After a successful ping returns a ping_accept status and a transaction_id, call this endpoint to submit the full lead — including all PII — and finalise the distribution to the matched buyer(s). This endpoint must only be called after a successful ping. The transaction_id from the ping response is required to link the two calls together.

Endpoint

Replace {source-unique-id} with the linkUniqueId for your source, found in your posting specification under the Post API section.

Authentication

Include the post-specific API token in the Authorization header:
The post token is separate from the ping and form tokens. All three are listed in your posting specification.

Request Parameters

Path Parameters

Body Parameters (JSON)

All campaign-specific custom fields sent in the ping should also be included in the post. Your posting specification lists required and optional fields for the Post API specifically.

Example Request

Example Responses

Success — Lead Sold

Success — Lead Unsold

Error — Missing Transaction ID

Error — Invalid Field

Status Codes

Tips

  • Always use the ping’s transaction_id. The post call is linked to the ping via this ID. Submitting a new or mismatched ID will result in a rejection.
  • Post promptly after ping. Ping acceptances have a time-to-live window. If the consumer takes too long to fill in the form, the bid may expire and the post could be rejected or unsold.
  • Include the same custom fields. Buyer evaluation during ping used the custom fields you sent. Include them again in the post for consistency and to avoid validation errors.
  • Redirect URL: Store redirect_url from the post response and redirect the consumer immediately to complete the buyer journey.
  • Do not reuse tokens across steps. The ping token and post token are different credentials. Using the wrong token returns a 401 error.