Integration

Send Swipe Pages leads to Juiced

This guide connects a Swipe Pages landing page form to a Juiced source. The route is Direct: the page level webhook integration takes an HTTP method, custom headers and your own webhook field names, so it can post straight to Juiced.

Reviewed October 2026 Reading time 6 min
The short version

Route: Direct. On the page's Integrations tab, add a Webhook with type Form Submission, choose POST, add Authorization and Content-Type headers and enter each Juiced key under Webhook fields.

You need a Swipe Pages plan with webhooks (check in your account; Global Webhooks are listed on the Agency plan) and a Juiced source with a bearer token and its field names from View API Spec.

The gotcha: page level webhooks are set up one page at a time, and Swipe Pages' docs do not state the body format. Check the first test in the post inspector before sending traffic.

Before you start

  • In Swipe Pages: a published page with a form on it (the webhook needs a form to exist first). The pricing page lists Global Webhooks on the Agency plan and does not say which plans include page level webhooks, so check the Integrations tab 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 page's webhook integration

    On the page dashboard, go to the Integrations tab, choose the Webhooks option at the bottom and click the Webhook button (Swipe Pages webhook docs).

  3. Enter the Juiced URL and choose Form Submission

    Enter a name, paste https://usejuiced.com/api/v1/leads into Webhook URL and select Form Submission as the Webhook Type (Payment Success sends order data instead). Click Continue, then Continue again.

  4. Set POST and add the headers

    Choose POST as the HTTP method. In the header fields add Authorization with Bearer, one space, then your token; Content-Type with application/json; and Accept with application/json.

  5. Enter Juiced keys as webhook field names

    Under Webhook fields, enter the Juiced key for each form field: first_name, last_name, email, phone, zip. Click Continue. On the next screen you can add extra webhook fields, then click Continue to finish.

  6. Send a test lead and check Incoming logs

    Submit the live page 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, check the headers and webhook field names, or use the Zapier route below. Turn test mode off before going live.

Field mapping

The key Juiced receives is the name you enter under Webhook fields.

Swipe Pages form fieldWebhook field (Juiced key)
First namefirst_name
Last namelast_name
Emailemail
Phonephone
Zip code (required)zip
Dropdown or radio questionA key you created in Juiced, such as credit_score_range
Hidden input with Load from URL onutm_source (create it in Juiced first)
TrustedForm certificate fieldtrusted_form_cert_url

For UTM values, add a hidden input to the form, give it a label and turn on the Load from URL toggle, per Swipe Pages' hidden field guide. Any extra key must exist as a field on the Juiced lead category or source (Fields tab > New field) or it is not saved.

Many pages on one domain. Global webhooks send from the pages you pick on one domain: Integrations > Global webhooks > Add Global Webhooks, pick the domain and pages, map fields, then choose a webhook format and headers and click Create Webhook. The setup steps for JSON delivery (format and Content-Type) are not in Swipe Pages' docs, so test one lead first.

Zapier route. If the webhook does not deliver JSON, use the Swipe Pages trigger New Form Submission in Zapier, map each field to its Juiced key and finish with the shared POST step in Zapier to Juiced.

Example request

With POST, the headers above and your webhook field names, 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": "facebook"
}

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

TrustedForm and Jornaya

Swipe Pages has no TrustedForm or Jornaya guide of its own. ActiveProspect's Web SDK article places the Certify snippet just before the closing body tag and lets you set its field parameter to a hidden input in your form. Add a hidden input for the certificate (and one for a Jornaya LeadiD if you use it), map each to a key you created in Juiced under Webhook fields, and check a test lead shows the values. Where to add page scripts depends on your plan (the pricing page lists Global Scripts on Agency), so check in your account. More in passing TrustedForm and Jornaya to Juiced.

Troubleshooting

  • Fields show in the log but are not on the lead. A webhook field name was left blank or does not match a field title in Juiced. Enter the exact key for every field you want saved.
  • 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's webhook field name is not 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.
  • Leads from another page never arrive. Page level webhooks cover one page. Repeat the setup on each page or use Global webhooks.
  • Order data arrives instead of the lead. The webhook type is Payment Success. Set it to Form Submission.

For more, see webhook troubleshooting.

Frequently asked

Does Swipe Pages have a webhook?

Yes. Swipe Pages has page level webhooks on each page’s Integrations tab and Global webhooks that cover many pages on one domain. Both take an HTTP method, headers and webhook field names.

Can Swipe Pages send leads to a lead distribution platform?

Yes. Point a Form Submission webhook at the platform’s endpoint, add its Authorization header and enter its field names under Webhook fields. Juiced then routes each lead to buyers by their bids, caps and criteria.

Which Swipe Pages plan do I need for webhooks?

The pricing page lists Global Webhooks on the Agency plan and does not say which plans include page level webhooks, so check the Integrations tab in your account.

How do I send UTM parameters from Swipe Pages?

Add a hidden input to the form, turn on Load from URL, and give it a webhook field name that matches a field you created in Juiced, such as utm_source.

How do I pass a TrustedForm certificate from Swipe Pages?

Install the TrustedForm Certify snippet on the page with its field parameter set to a hidden input, then map that input under Webhook fields to a Juiced key such as trusted_form_cert_url.

From Juiced

Route every Swipe Pages lead to the right buyer

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

Book a demo

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.