If we imagine a scenario where your buyer's system is sending back an API response similar to the below and you want to send back the "redirect_url" and "price" values to your supplier to be used in their submission flow.

{
 "status": "success",
 "code": 200,
 "message": "Lead accepted",
 "redirect_url": "https://google.com",
 "price": "20"
}

This is possible with Live Buyer Responses.
 
You have two options for how this can be done, both require you to first enable Liver Buyer Responses in the campaign's advanced settings. The advanced settings are located at the bottom of the campaign settings.
 

Sending the whole RAW response back to the supplier.

The first option would be to send back the whole RAW response to the supplier.
 
You would need to go into the API key doing the lead submissions and enter the "API Queue" options.
 

 
In the delivery information section you would select "Approved" for lead status and "Raw Response" under fields.
 

With this setup, the whole response would be output into the API response on submission:
 

 { 
   "status": "Success", 
   "code": 1, 
   "message": "OK", 
   "records": [ 
       { 
           "queueId": "ac1e0bf2-3656328b-69c55e77-6649-89fb6bcc", 
           "status": "Approved", 
           "processed": "2026-03-26T16:27:35Z", 
           "response": { 
               "code": 1, 
               "response": "OK", 
               "info": [], 
               "leadId": 5119351, 
               "rejectionId": null, 
               "redirectUrl": "", 
               "processTime": 1.08, 
               "timestamp": "2026-03-26T16:27:35Z" 
           }, 
           "deliveryStatus": "Complete", 
           "deliveriesProcessed": 1, 
           "deliveryCount": 1, 
           "deliveries": [ 
               { 
                   "rawResponse": "{\r\n  \"status\": \"success\",\r\n  \"code\": 200,\r\n  \"message\": \"Lead accepted\",\r\n  \"redirect_url\": \"https://google.com\",\n  \"price\": \"20\"\n}" 
               } 
           ] 
       } 
   ] 
}

Sending only parts of the response back to the supplier.

The alternative option would need you to set up mapping onto the delivery, to map the "redirect_url" value and the "price" value into standard LeadByte fields on each lead. 

As API keys can apply to multiple campaigns at once, you cannot map response values into custom fields, only standard fields can be used. 

The C1 / C2 / C3 values are useful for this application.
 
In the remote system response section of the delivery that is responding with the API response we want to map, if you edit the success response, you can assign part of a response to the lead with JSON path as shown here.
 

For the buyer response:

 {
 "status": "success",
 "code": 200,
 "message": "Lead accepted",
 "redirect_url": "https://google.com",
 "price": "20"
}

$.redirect_url will target the "redirect_url" field.
$.price will target the "price" field.

Assign delivery response to a lead field - This article goes into more detail.
 
This will result in whenever the success response is sent back on lead delivery, the "redirect_url" and "price" values will be mapped to C1 and C2 on that lead.
 
Back to the "API queue" settings on the API key. This time we will scroll down to "Lead information" - select "Approved" for lead status and then select both the C1 and C2 fields in the dropdown.

 

Now when a lead is submitted, this is the response:
 

{ 
   "status": "Success", 
   "code": 1, 
   "message": "OK", 
   "records": [ 
       { 
           "queueId": "ac1e0ac0-3656328b-69c5614e-b206-cbac3eb4", 
           "status": "Approved", 
           "processed": "2026-03-26T16:39:42Z", 
           "response": { 
               "code": 1, 
               "response": "OK", 
               "info": [], 
               "leadId": 5119367, 
               "rejectionId": null, 
               "redirectUrl": "", 
               "processTime": 1.07, 
               "timestamp": "2026-03-26T16:39:42Z" 
           }, 
           "deliveryStatus": "Complete", 
           "deliveriesProcessed": 1, 
           "deliveryCount": 1, 
           "lead": { 
               "received": "2026-03-26T16:39:42Z", 
               "id": 5119367, 
               "c1": "https://google.com", 
               "c2": "20" 
           } 
       } 
   ] 
}

 
If you look through the "API Queue" options, you can see all the different data types that can be sent back to the supplier in the API response.