Send LeadsPedia leads to Juiced
This guide adds Juiced as a buyer in LeadsPedia, with a delivery method that posts each lead to the Juiced API as JSON, or pings first and posts with the ping ID.
Route: Lead platform as buyer. In LeadsPedia, Juiced becomes an advertiser with a lead distribution contract, and a Post or Ping Post delivery method sends JSON to the Juiced API.
LeadsPedia's public docs do not show the delivery method settings screen, so this guide lists the exact values to give LeadsPedia support or your account manager: endpoint, headers, JSON keys and response rules. You need a Juiced source and its bearer token.
The gotcha: Juiced answers 201 for sold and unsold leads alike. The delivery must count a lead as accepted only when data.status is accepted.
Before you start
- In LeadsPedia: rights to add advertisers and lead distribution contracts, or an account manager who can. The LeadsPedia API shows how the pieces fit: a lead distribution contract belongs to an advertiser and a vertical, has a revenueModel of Fixed or Ping/Post and a mode of Setup, Test or Live, and delivery methods come in types including Post and Ping Post (lead contracts, delivery methods).
- 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 LeadsPedia to send you leads, and Internal when the leads are your own. A ping returns its id in
data.id, and the post carries it asping_id. A vendor source reads its price fromdata.price(ping reference). - Optional partner header. If Juiced gave you a partner ID for partner-attributed traffic, add
X-Partner-Id. Leave it out otherwise.
Step by step
-
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 and keep the link. See setting up a source.
-
Add Juiced as an advertiser and contract
Create an advertiser for Juiced and a lead distribution contract under it for the vertical. Choose Ping/Post as the revenue model if you will ping Juiced first, or Fixed for a set price. Labels in the LeadsPedia interface may differ from the API names, so check in your account.
-
Send LeadsPedia the delivery values
Ask LeadsPedia support or your account manager to set up a Post or Ping Post delivery method on the contract with the values in the table below, and share your View API Spec link. If you configure delivery methods yourself, enter the same values.
-
Test in Test mode
With the contract in Test mode, send a lead with zip
00001(accepted) and one with00003(rejected). In Juiced, check Entries > Incoming logs with the Test only filter and confirm LeadsPedia recorded the first as accepted and the second as not sold. -
Go live
Turn off Test mode on the Juiced source, then set the contract to Live and its status to Active.
LeadsPedia's public docs do not confirm that a delivery method can send a JSON body with an Authorization header. On the first test, open the log in Juiced and check the post inspector: the Request should show top-level JSON keys, and the response should not be 401. If LeadsPedia cannot send that format, post the lead to a webhook in Zapier or Make and send the JSON POST to Juiced from there.
What to give LeadsPedia
| Setting | Value |
|---|---|
| Post endpoint | POST https://usejuiced.com/api/v1/leads |
| Ping endpoint (Ping Post) | POST https://usejuiced.com/api/v1/ping, with only the fields marked Required for ping (always zip) |
| Headers | Authorization: Bearer <token>, Content-Type: application/json, Accept: application/json, optional X-Partner-Id |
| Body | JSON, top-level keys named exactly as the Juiced field Titles. No nested objects, form encoding or token in the URL |
| Ping to post | Every valid ping returns 200. Post only when data.status is matched; read the price from data.price and send data.id as ping_id in the post body |
| Accepted when | HTTP 201 and data.status equals accepted (check the path syntax in your account) |
| Price field | data.price in the post response |
| Reference ID | data.id |
Field mapping
| Juiced key | LeadsPedia field |
|---|---|
first_name, last_name | The vertical's first and last name fields |
email, phone | Email and phone fields |
zip | Zip code. Always required, on the ping and the post |
| Custom answers, sub IDs, UTM values | Keys you add on the Juiced source's Fields tab first |
trusted_form_cert_url or jornaya_leadid | The field holding the certificate URL or LeadiD, if collected |
Example request
POST https://usejuiced.com/api/v1/leads
Authorization: Bearer <your token>
Content-Type: application/json
Accept: application/json
{
"ping_id": "ping_01HZX4K2M8",
"first_name": "Jane",
"last_name": "Doe",
"email": "jane@example.com",
"phone": "5555550100",
"zip": "00001"
}Leave out ping_id for a Post delivery method. See the leads and ping API references.
Response parsing
| Juiced returns | Meaning | LeadsPedia should record |
|---|---|---|
Ping 200: data.status matched | Juiced wants the lead at data.price | Post with ping_id = data.id |
Ping: no_match, duplicate, rejected | Juiced does not want the lead | Do not post |
201 + data.status accepted | Sold or accepted, with its data.price | Accepted, at data.price |
201 + data.status rejected | Received, not sold, price 0 | Rejected |
201 + data.status duplicate | Duplicate, price 0 | Rejected as duplicate |
401 unauthenticated | Missing or invalid credentials | Error. Fix the Authorization header |
422 | Read error.code (for example validation_failed or ping_mismatch) and the field errors | Error. Fix the field and resend |
The data.status values are Juiced's default mapping. Confirm them on your source's API spec.
TrustedForm and Jornaya
LeadsPedia lists TrustedForm and Jornaya among its integrations (LeadsPedia). To pass a certificate URL or LeadiD on, 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 include it in the delivery's field mapping. See passing TrustedForm and Jornaya to Juiced.
Troubleshooting
- Unsold leads count as accepted. The delivery checks only the HTTP code. Accept only when
data.statusequalsaccepted. - Unauthorized (401). A line break or extra space crept into the header. A new Juiced token also expires the old one 24 hours later, so update the delivery first.
- 422 on the post after a ping. Read
error.codein the response:ping_mismatchmeans the post does not match its ping. Check thatping_idcarriesdata.idand the post repeats the same ping fields. - Fields missing in Juiced. A key does not match a Juiced field Title. Open the log's post inspector to see the payload as received.
More fixes in webhook troubleshooting.
Frequently asked
Can LeadsPedia send leads to Juiced?
Yes. Set Juiced up as an advertiser with a lead distribution contract and a Post or Ping Post delivery method that sends JSON to the Juiced API with a bearer token header.
What do I give LeadsPedia support to set up Juiced?
The post and ping endpoints, the Authorization, Content-Type and Accept headers, the JSON keys from View API Spec, and the rule that a lead is accepted when Juiced returns HTTP 201 with data.status accepted, with the price in data.price.
Does Juiced support ping post from LeadsPedia?
Yes. LeadsPedia can ping the Juiced v1 ping endpoint and, when data.status is matched, post the full lead with ping_id set to data.id.
Should the Juiced source be Vendor or Internal?
Use Vendor when a vendor uses LeadsPedia to send you leads, and Internal when the leads are your own.
How do I pass a TrustedForm certificate from LeadsPedia to Juiced?
Add a field such as trusted_form_cert_url to the Juiced lead category or source and include it in the delivery method’s field mapping.
Route LeadsPedia traffic to the right buyer
Juiced routes each lead to your buyers by bids, caps and criteria, and moves unsold leads to your marketplace.
Scale your lead business, without limits
Juiced puts you in full control of your leads, routing, and revenue, so you can automate, optimize, and grow without chaos.