JuicedJuiced
Integration

Send LeadConduit leads to Juiced

This guide adds Juiced as a recipient in an ActiveProspect LeadConduit flow, using the JSON integration to post each lead to the Juiced API with a bearer token.

Reviewed October 2026 Reading time 5 min
The short version

Route: Lead platform as buyer. In your LeadConduit flow, click Add to Flow > Integration, choose the JSON type, enter the Juiced URL with Bearer Token authentication, and map each field as a JSON Property.

You need edit access to the flow, plus a Juiced source, its bearer token, and the field names from View API Spec. LeadConduit's public docs describe outbound delivery as a single post, so this is a direct post setup.

The gotcha: Juiced answers 201 for sold and unsold leads alike. Set Outcome Search Term to accepted with Outcome Search Path data.status, or rejected leads look successful.

Before you start

  • In LeadConduit: a flow that receives the leads, and rights to edit it in the Flows tab (Recipient Integrations).
  • 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 LeadConduit to send you leads, and Internal when the leads are your own. Juiced also has a v1 ping endpoint that returns a ping id in data.id, but LeadConduit's public docs do not describe pinging a recipient, so post the full lead.
  • Optional partner header. If Juiced gave you a partner ID for partner-attributed traffic, add an X-Partner-Id header. 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 JSON integration to the flow

    In the Flows tab, edit the flow, click Add to Flow, select Integration and choose the JSON type. Name the step and click Next (JSON integration).

  3. Set authentication and the URL

    Choose Bearer Token as the authentication type and paste the Juiced token. LeadConduit's docs say to add a Header mapping of Authorization: Bearer TOKEN, where it swaps in the stored token. Enter https://usejuiced.com/api/v1/leads under Url and keep the method as POST. Add Accept: application/json the same way, and for X-Partner-Id if you use one.

  4. Configure response parsing

    Juiced wraps the result in data, and LeadConduit reads JSON responses with dot-notation paths. Set Outcome Search Term to accepted and Outcome Search Path to data.status, and leave Outcome On Match at its default, success. Set Price Path to data.price, Reason Path to data.status and Reference Path to data.id. Then choose whether failed leads continue or stop.

  5. Map the fields

    Open Field Mappings, select each LeadConduit field on the left, choose JSON Property on the right and enter the Juiced key, such as first_name. Paths are case-sensitive. Keep every key top-level, with no dots, because dot notation nests the value and Juiced does not read nested objects.

  6. Submit a test lead

    Save the flow and submit a test lead with zip 00001 (accepted), then one with 00003 (rejected). Check the outcome in the lead's event details in LeadConduit (the exact screen name is not in its public docs, so check in your account), and in Juiced under Entries > Incoming logs with the Test only filter. Then turn off Test mode on the Juiced source.

Field mapping

LeadConduit fieldJSON Property (Juiced key)
First and last name fieldsfirst_name, last_name
Email and phone fieldsemail, phone
Zip code fieldzip (always required)
Custom fields, sub IDs, UTM valuesKeys you add on the Juiced source's Fields tab first
TrustedForm certificate URLtrusted_form_cert_url, once the field exists in Juiced

Example request

POST https://usejuiced.com/api/v1/leads
Authorization: Bearer <your token>
Content-Type: application/json
Accept: application/json

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

See the leads API reference.

Response parsing

Juiced returnsMeaningLeadConduit outcome
201 + data.status acceptedSold or accepted, with its data.pricesuccess, price from data.price
201 + data.status rejectedReceived, not sold, price 0failure, reason rejected
201 + data.status duplicateDuplicate, price 0failure, reason duplicate
401 unauthenticatedMissing or invalid credentialsfailure. Fix the bearer token
422error.code (for example validation_failed) and the field errorsfailure. Fix the mapping and resend

The data.status values are Juiced's default mapping. Confirm them on your source's API spec. If LeadConduit misreads the body, its Response Content-Type Override mapping can force JSON parsing (Response Parsing Overview).

TrustedForm and Jornaya

LeadConduit can add TrustedForm to the flow: add an Add-On step, search for TrustedForm, pick the products you use (Retain, Insights or Verify), click Finish and save the flow (TrustedForm Add-On). To pass the certificate URL or a Jornaya 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 buyers ask for it, and map it as a JSON Property. See passing TrustedForm and Jornaya to Juiced.

Troubleshooting

  • Rejected leads show as success. The outcome term is too broad or has no path. Use term accepted with path data.status.
  • Unauthorized (401). The token has a trailing space or line break, or was replaced in Juiced; a new token expires the old one 24 hours later.
  • Fields missing in Juiced. A JSON Property used dot notation, which nests the value, or does not match a Juiced field Title exactly.
  • List values rejected (422). A List of Values field got a value Juiced does not list. Change the value in the flow before the recipient step.

More fixes in webhook troubleshooting.

Frequently asked

Can LeadConduit send leads to Juiced?

Yes. Add a JSON integration recipient to your LeadConduit flow that posts to the Juiced API with Bearer Token authentication and maps each field as a JSON Property.

How should LeadConduit read the Juiced response?

Set Outcome Search Term to accepted and Outcome Search Path to data.status, Price Path to data.price, Reason Path to data.status and Reference Path to data.id. Juiced returns HTTP 201 for sold and unsold leads, so data.status decides the outcome.

Can LeadConduit ping Juiced before posting?

LeadConduit’s public docs describe recipient delivery as a post, not an outbound ping, so send the full lead. Juiced’s ping endpoint is available for platforms that support a custom ping.

Can LeadConduit add TrustedForm to leads sent to Juiced?

Yes. LeadConduit has a TrustedForm Add-On step for flows. Add a field such as trusted_form_cert_url to the Juiced source and map the certificate URL to it.

Should the Juiced source be Vendor or Internal?

Use Vendor when a vendor uses LeadConduit to send you leads, and Internal when the leads are your own.

From Juiced

Route LeadConduit traffic to the right buyer

Juiced routes each lead to your buyers by bids, caps and criteria, and moves unsold leads to your marketplace.

Book a demo

All integrations Webhook troubleshooting TrustedForm and Jornaya Lead Prosper to Juiced LeadByte to Juiced Custom code to Juiced

This guide describes common commercial practice in the lead-generation industry. It is not legal advice, so take advice on your own arrangement. Where this site refers to consent or contact rules, it points to the source rather than restating the rule; those sources are listed in the glossary.

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.

Get a demoView pricing