Send Lead Prosper leads to Juiced

Before you start

• In Lead Prosper: a campaign whose fields cover what Juiced needs (at least zip), and access to add buyers to it. Lead Prosper says every buyer runs independently in its campaign with its own pricing, caps, filters, payload and response mapping (What is a buyer).
• In Juiced: a source, its bearer token, and the endpoint and field names from View API Spec.
• Pick the source type. Use Vendor when a vendor uses Lead Prosper to send you leads, and Internal when the leads are your own. A ping returns its id in data.id, and the post then carries it as ping_id. A vendor source reads its price from data.price (ping reference).
• Optional partner header. If Juiced gave you a partner ID for partner-attributed traffic, also send X-Partner-Id. Leave it out otherwise.

Step by step

1. Create a source in Juiced and copy a token

   Go to Ingest > Sources > New source, set the Source type, turn on Test mode and click Create source. On the Authentication tab click New bearer token > Create token and copy it. Open Overview > More actions (⋯) > View API Spec for the endpoint and field names. See setting up a source.

2. Add a buyer to the campaign

   In the campaign, add a buyer and choose Direct Post for one request per lead, or Ping Post to ping first and post only after Juiced accepts (buyer types). Lead Prosper says new buyers are set to Paused by default (What is a buyer). The articles do not name the button to add one, so check in your account.

3. Set the request

   In the Payload Builder, set Request Type to POST and Posting URL to https://usejuiced.com/api/v1/leads. Choose JSON as the payload type. Under Headers add Authorization with Bearer and your token, and Accept: application/json. Lead Prosper fills Content-Type from the payload type (Payload Builder, Direct Post setup).

4. Build the JSON payload

   Add one key per Juiced field and insert the campaign field token as its value, for example first_name = {{first_name}}. Keys must match the Juiced field Title exactly, including case.

5. Set up the ping (Ping Post only)

   Set the ping URL to https://usejuiced.com/api/v1/ping with the same headers, and send only the fields marked Required for ping (always zip). Every valid ping returns 200, so read the body. In the Response Parser for the PING step, paste a sample Juiced ping response, select matched in /data/status and choose ACCEPTED. Select the price in /data/price and choose Real-Time Price, then click Apply Configuration. In the post payload add ping_id with the {{lp_ping_response:KEY}} token the parser generates when you select the id under data (check the path syntax in your account) (Ping Post buyer setup, Response Parser Tool).

6. Map the post response

   In the Response Parser, paste a sample Juiced post response. Select accepted in /data/status and choose ACCEPTED, then select duplicate and choose DUPLICATED. Lead Prosper writes nested keys as slash paths, as in its /bids/0/payout example. Click Apply Configuration. Price options for a Direct Post buyer vary, so check in your account (Response Parser Tool).

7. Test, then resume the buyer

   Save, open the Test Buyer Tool, and send a lead with zip 00001 (accepted) and another with 00003 (rejected). In Juiced, check Entries > Incoming logs with the Test only filter. When results match, turn off Test mode in Juiced and click Resume on the buyer (test and go live).

Field mapping

Example request

Headers on the ping and the post:

Authorization: Bearer <your token>
Content-Type: application/json
Accept: application/json
X-Partner-Id: <partner ID, optional>

Post body as Lead Prosper sends it after an accepted ping:

{
  "ping_id": "ping_01HZX4K2M8",
  "first_name": "Jane",
  "last_name": "Doe",
  "email": "jane@example.com",
  "phone": "5555550100",
  "zip": "00001"
}

For a Direct Post buyer, send the same body without ping_id. See the leads and ping API references. Responses wrap the result in data.

Response parsing

Set the Lead Prosper response parser so it reads Juiced's answers like this:

The data.status values above are Juiced's default mapping. Confirm them on your source's API spec before you go live.

TrustedForm and Jornaya

If your Lead Prosper campaign collects a TrustedForm certificate URL or a Jornaya LeadiD, add a field such as trusted_form_cert_url or jornaya_leadid to the Juiced lead category or source, mark it Deliverable if your buyers ask for it, and add that key to the post payload. Details are in passing TrustedForm and Jornaya to Juiced.

Troubleshooting

• Every lead shows as accepted. ACCEPTED is mapped to the HTTP status code instead of the status value. Juiced answers 201 for sold and unsold leads, so map ACCEPTED to /data/status equal to accepted only.
• Unauthorized (401). A space after Bearer is missing or doubled, or a line break was pasted with the token. A new token also expires the old one 24 hours later.
• 422 on the post after a ping. Read error.code in the response: ping_mismatch means the post does not match its ping. Check that ping_id carries data.id from the ping and the post repeats the same ping fields.
• Fields missing in Juiced. A payload key does not match a Juiced field Title. Copy the keys from View API Spec.
• Test leads land in Audit. The zip was not a test zip, or test mode was off. Use 00001 to 00005.

More fixes in webhook troubleshooting.

Frequently asked