Live Buyer Responses

Live Buyer Responses provides a real‑time outcome for every lead once it has finished processing across all Buyers. It allows you to instantly redirect customers based on who purchased the lead, or give Suppliers an immediate “sold/not sold” response for billing and reporting. This article explains how to enable the feature, configure your REST API Key, and interpret the different response types.

Requirements for Live Buyer Responses
To use Live Buyer Responses, ensure the following:

The Campaign is set to Buyer Delivery Accept
Leads are submitted using the REST API (Version 1.3)
Live Buyer Responses is enabled on the Campaign

Using Live Buyer Responses on Your Own Landing Pages

If you want to redirect customers based on the Buyer outcome:
Configure your REST API Key to include Buyer information (Admin Key recommended)
Handle the JSON response on your website to perform the redirect

Using Live Buyer Responses for Suppliers

If you want Suppliers to receive a real‑time billable response:

Use a Supplier REST API Key
Suppliers should treat a lead as billable when the Status in the records array is "Approved"

REST API Key Configuration (Admin Key)

When creating your REST API Key:

Ensure it is API Version 1.3
Enable Create Lead permission
Under API Queue Settings, configure:

Setting	What to Select
Append Buyer Data	Approved
Include Buyer Fields	Any Buyer fields you want returned (e.g., Buyer Name)
Include Buyer Statuses	Sold

Enabling Live Buyer Responses

Go to Update Campaign Settings
Scroll to Advanced Settings
Tick Live Buyer Responses
Save your changes

Example Response (Admin Key showing extra data)

Approved Lead

{
   "status": "Success",
   "code": 1,
   "message": "OK",
   "records": [
       {
           "queueId": "ac1e0206-12eaee18-63765b37-471b-f60cd31d",
           "status": "Approved",
           "processed": "2022-11-17T16:03:04Z",
           "response": {
               "code": 1,
               "response": "OK",
               "info": [],
               "leadId": 7185867,
               "rejectionId": null,
               "redirectUrl": "",
               "processTime": 1.04,
               "timestamp": "2022-11-17T16:03:03Z"
           },
           "deliveries": [
               [],
               [],
               []
           ],
           "buyers": [
               {
                   "id": "59",
                   "name": "Buyer 2",
                   "reference": "2"
               }
           ]
       }
   ]
}

Rejected Lead

{
    "status": "Success",
    "code": 1,
    "message": "OK",
    "records": [
        {
            "queueId": "ac1e01fb-36a661b0-63765c64-8e7f-a35bba7d",
            "status": "Rejected",
            "processed": "2022-11-17T16:08:05Z",
            "response": {
                "code": 1,
                "response": "OK",
                "info": [],
                "leadId": 7185879,
                "rejectionId": null,
                "redirectUrl": "",
                "processTime": 1.03,
                "timestamp": "2022-11-17T16:08:04Z"
            },
            "deliveries": []
        }
    ]
}

Rejected at Campaign Level

{
    "status": "Error",
    "code": -2,
    "message": "One or more errors occurred, see errors array",
    "redirectUrl": "",
    "errors": [
        "Lead was detected as being a duplicate"
    ]
}

Supplier Key Response (minimal data)

Approved Lead

{
    "status": "Success",
    "code": 1,
    "message": "OK",
    "records": [
        {
            "queueId": "ac1e0b29-3656328b-690de463-986f-d79764dd",
            "status": "Approved",
            "processed": "2025-11-07T12:21:55Z",
            "response": {
                "code": 1,
                "response": "OK",
                "info": [],
                "leadId": 123,
                "rejectionId": null,
                "redirectUrl": "",
                "processTime": 1.09,
                "timestamp": "2025-11-07T12:21:55Z"
            }
        }
    ]
}

Rejected Lead

{
    "status": "Success",
    "code": 1,
    "message": "OK",
    "records": [
        {
            "queueId": "ac1e0b29-3656328b-690de423-7d85-4a3c3687",
            "status": "Rejected",
            "processed": "2025-11-07T12:20:51Z",
            "response": {
                "code": 1,
                "response": "OK",
                "info": [],
                "leadId": 119,
                "rejectionId": null,
                "redirectUrl": "",
                "processTime": 1.07,
                "timestamp": "2025-11-07T12:20:51Z"
            }
        }
    ]
}

Rejected at Campaign Level

{
    "status": "Error",
    "code": -2,
    "message": "One or more errors occurred, see errors array",
    "redirectUrl": "",
    "errors": [
        "Lead was detected as being a duplicate"
    ]
}

FAQ

How do I include the Buyer Name in the response?
Select Buyer Name under Include Buyer Fields in your REST API Key settings.

How do I include lead data in the response?
Select the required fields under Include Lead Fields in your REST API Key.

What affects the speed of a Live Buyer Response?
The response time depends on how long it takes all Buyers’ APIs to respond.

Why am I still seeing “Queued” even though Live Buyer Responses is enabled?
Your request may not be following redirects. Ensure your application or Supplier system follows HTTP redirects.

LeadByte Support

Comments