Skip to main content
GET
cURL

Overview

The Fetch Form Submission API retrieves the stored response data for a previously submitted lead. Use it to look up the distribution outcome, buyer response, deduplication result, or redirect URL associated with a specific transaction_id. This is useful for debugging integrations, auditing lead outcomes, and building confirmation pages that display post-submission results.

Endpoint

Replace :sourceID with the source unique ID. The transaction_id is passed as a query parameter to identify the specific lead.

Authentication

Include your API token in the Authorization header:

Request Parameters

Path Parameters

Query Parameters

Example Request

Example Responses

Success — Lead Response Found

Success — Duplicate Lead

Error — Lead Not Found

Error — Unauthorized

Status Codes

Tips

  • Immediate availability: Response data is available as soon as the lead submission completes. In most cases, you can fetch it within a few milliseconds of the original POST.
  • Debugging submissions: If a landing page integration is not behaving as expected, use this endpoint to confirm what the platform recorded and returned during distribution.
  • Redirect URL delivery: If your form does not capture the redirect_url from the submission response, you can re-fetch it here and redirect the consumer server-side.
  • Deduplication flag: The isDeDupe field lets you determine whether the consumer had previously submitted through this campaign.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

campaign-id
string
required

Your campaign ID

Query Parameters

transaction_id
string
required

Your lead transaction ID

Response

Lead successfully matched

status
string

Status code of API response

type
string

Type of API response which can be success or error

message
string

Message of API response