Send Landingi leads to Juiced

Before you start

• In Landingi: a landing page with a form and access to the editor. The pricing page lists a POST & Webhook row across the Build, Optimize, Scale and Enterprise plans; check which plans tick it, or check in your account.
• In Juiced: a source for these leads, a bearer token from its Authentication tab, and the exact field names from View API Spec. Turn on Test mode on the source while you set up.

Step by step

1. Create a Juiced source and copy a bearer token

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

2. Open the form's Webhook integration

   In Landingi, open the page in the editor and go to the form Settings. On the Integrations tab choose Webhook (or type it in the search bar and press enter), per Landingi's webhook docs.

3. Set the request URL and method

   In Request URL, enter https://usejuiced.com/api/v1/leads. In Request method, select POST.

4. Map the form fields to Juiced keys

   Under Connect the form fields, enter the Juiced key next to each form field: first_name, last_name, email, phone, zip. Map answers and hidden fields to keys you have created in Juiced.

5. Add the request headers

   In Request headers, enter Key Authorization and Value Bearer, one space, then your token. Click + and add Content-Type with application/json, then Accept with application/json. Leave Request parameters empty unless you want to send a fixed value, such as a sub ID field you created in Juiced.

6. Save and publish the page

   Click Save and close, then publish the landing page so the integration runs on the live page.

7. Send a test lead and check Incoming logs

   Submit the live form with zip 00001. In Juiced, open Entries > Incoming logs, filter Test mode to Test only, open the log and click Post to see the payload, any Validation errors and the response. If the request shows no fields or a 422 for every required field, Landingi sent form data: switch to the Zapier or Make route below. Turn test mode off before going live.

Field mapping

The key Juiced receives is the name you enter for each field under Connect the form fields, plus any key you add under Request parameters.

For UTM values, Landingi's UTM guide adds one Hidden fields element per parameter (Form fields tab > Add element), sets Field value of the name attribute to the parameter name, and adds its matching script on the page's JavaScript Codes tab at Body bottom. Any extra key must exist as a field on the Juiced lead category or source (Fields tab > New field) or it is not saved.

Zapier or Make route. If the webhook arrives as form data, use the Landingi trigger New Lead From Landing Page in Zapier (there are also triggers for Lightbox and PopUp forms), map each field to its Juiced key and finish with the shared POST step in Zapier to Juiced or Make to Juiced.

Example request

With POST, the headers above and your mapped keys, Juiced expects:

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",
  "utm_source": "google"
}

A 201 response with data.status accepted means the lead was accepted. See the leads endpoint reference.

TrustedForm and Jornaya

Jornaya's Landingi guide adds a Hidden form field named leadid_token with an empty value, then pastes a callback script and the campaign script into an HTML element at the bottom of the page. For TrustedForm, add the Certify snippet on the page's JavaScript Code tab (Add new script, Position body bottom), per Landingi's custom JavaScript article, and set the snippet's field parameter to a hidden field you added to the form (ActiveProspect's Web SDK article). Map both fields to keys you created in Juiced and check a test lead shows the values. More in passing TrustedForm and Jornaya to Juiced.

Troubleshooting

• The log shows no fields, or every required field fails. The body was not JSON. Check the Content-Type header, then use Zapier or Make if it persists.
• 401 Unauthorized (unauthenticated). The header value must be Bearer, one space, then the token, with no trailing space or line break. A new token expires the previous one 24 hours later.
• 422 with a zip error. The zip field is not mapped to exactly zip. Open the log's Post view to see the keys as received. Juiced returns error.code validation_failed with errors keyed by field.
• Nothing arrives. The integration belongs to one form. Check you edited the form visitors use, clicked Save and close and published.
• Hidden field values are empty. The name attribute must match the URL parameter exactly, and the UTM script must be on the Main page at Body bottom.

For more, see webhook troubleshooting.

Frequently asked