Send leads to Juiced by webhook: setup and troubleshooting

What any tool needs to send

Juiced documents one format: a JSON body with top-level keys, sent with an auth header. If your tool can do this, connect it directly. If it cannot (it only sends form-encoded data, nests fields inside an object, or cannot add headers), send the lead through Zapier or Make instead.

Bearer token or Basic auth

Both credentials live on the source's Authentication tab. A bearer token is the simpler choice for most tools. Click New bearer token, then Create token, and copy it right away: it is shown once.

Authorization: Bearer YOUR_TOKEN

Use exactly one space after Bearer, and no spaces or line breaks inside or after the token. Creating a new token expires the previous one 24 hours later.

For Basic auth, the API Key is the username and the API Secret is the password. If your tool has username and password fields for Basic auth, enter them there. If you must type the header yourself, the standard Basic format is the key and secret joined by a colon, base64-encoded:

Authorization: Basic <base64 of api_key:api_secret>

The key and secret cannot be regenerated.

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": "5555550123",
  "zip": "00001"
}

Finding your field names

Open the source, then Overview > More actions (⋯) > View API Spec. The page shows your credentials, the exact endpoint URL, an example cURL request and the Field Reference: every accepted field with its type and whether it is Required for post or Required for ping. The link expires after 7 days; open View API Spec again for a fresh one.

Keys are snake_case, for example first_name, last_name, email, phone, address_1, city, state and zip. To accept a field that is not listed, add it on the lead category (Ingest > Lead Categories) or on the source's Fields tab with New field: set the Title, Type, Required for post, Required for ping and Deliverable (on if buyers should receive it). A title may use letters, numbers and underscores only and must start with a letter or underscore. See setting up a source.

Step by step

1. Create a source and copy a token

   In Juiced, go to Ingest > Sources > New source, fill in the form and click Create source. On the Authentication tab, create a bearer token and copy it.

2. Open View API Spec

   Copy the endpoint URL and note the field names in the Field Reference. Add any missing fields before you map.

3. Set up the request in your tool

   Enter the URL, method and headers from the table above, choose a JSON body, and map each form field to its Juiced key. Our per-tool guides on the integrations hub show where each setting lives.

4. Turn on test mode and send a test lead

   Edit the source and turn on Test mode. Submit a lead from your tool with a test zip code from the table below.

5. Check Incoming logs

   Open Entries > Incoming logs, set the Test mode filter to Test only, and open the post inspector to confirm the payload and response.

6. Turn off test mode and go live

   Edit the source and turn Test mode off before sending live leads.

Testing with test zip codes

With test mode on, these zip codes return fixed results under the default status mapping.

Reading the result

Juiced answers every post. A 201 Created returns data.id, data.status and data.price (what the source earns, 0 unless accepted). By default, accepted means assigned, posted to a partner, marketplace or Club; rejected means Unassigned, Audit or Uncategorized (received but not sold); the third status is duplicate. Errors return error.code; branch on the code, not the message. A 401 is unauthenticated. A 422 is validation_failed with an errors object keyed by field, quota_reached or ping_mismatch; fix the payload and resend. Details: v1 leads endpoint.

To see what arrived, open Entries > Incoming logs (newest first), open the log, then click Post under Records. The post inspector shows:

• Request: the payload as received, including keys that do not map to a field, and Validation errors field by field if the post was rejected.
• Response: what Juiced sent back.
• Details: whether the post was Accepted or Rejected, and the response code (201 or 422).

More in the logs docs.

Troubleshooting

Frequently asked