Lead Recorder API reference (Zapier, Make, Pabbly, n8n & Wix)

The complete reference for every Lead Recorder endpoint that accepts a personal API key: authentication, the Zapier/Make New Lead trigger, connecting via Pabbly Connect or n8n, and the Wix app's site-linking endpoint.

The Lead Recorder Zapier and Make apps let you send new leads into any other tool (a CRM, Slack, a spreadsheet) the moment they're captured on your site, and the Wix app uses the same key to link a Wix site to a Lead Recorder account. All four authenticate with the same personal API key, and the same endpoints work directly from Pabbly Connect or n8n using their generic HTTP Request actions, no dedicated Lead Recorder app required in either. This page documents every endpoint reachable with that key, for reviewers and for anyone building against it directly. It does not cover the separate OAuth-based API our MCP server uses for AI assistant connections (Claude, Gemini, Grok); that has its own reference at /docs/mcp-server.

Authentication

Every request is authenticated with a personal API key, sent as a header:

X-Api-Key: lr_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Generate a key from your Lead Recorder dashboard under Account → API access. Keys are account-scoped: a key grants access to whatever sites the generating user can already see (an admin sees every site on the account, a client only the sites they've been given access to). Regenerating a key immediately invalidates the previous one. A request with a missing or invalid key returns 401 Unauthorized.

GET /api/zapier/auth/test

Validates an API key. This is the endpoint Zapier or Make calls when a user connects their account.

curl -H "X-Api-Key: lr_xxx" https://www.leadrecorder.com/api/zapier/auth/test

200 OK
{ "email": "you@example.com" }

GET /api/zapier/sites

Lists the sites the authenticated account can access. Powers the site dropdown on the New Lead trigger.

curl -H "X-Api-Key: lr_xxx" https://www.leadrecorder.com/api/zapier/sites

200 OK
[
  { "id": "abc123", "name": "My Website", "domain": "example.com" }
]

GET /api/zapier/leads

Returns leads for a given site, newest first: the data source behind the New Lead trigger. Requires a siteId query parameter, and 404s if the authenticated account can't access that site. An optional limit query parameter caps the number of leads returned; it can only lower the cap, never raise it past the site owner's plan limit, which applies regardless (same as the leads list in the dashboard). gclid, gbraid, and fbclid are included specifically so Zap/Make templates that upload offline conversions back to Google Ads or Meta have a click ID to attribute against — they're null when a lead didn't come from a paid click.

curl -H "X-Api-Key: lr_xxx" \
  "https://www.leadrecorder.com/api/zapier/leads?siteId=abc123&limit=10"

200 OK
[
  {
    "id": "lead_abc123",
    "submittedAt": "2026-07-28T04:32:10.000Z",
    "status": "new",
    "type": "form",
    "formPage": "/contact",
    "nameField": "Jane Smith",
    "emailField": "jane@example.com",
    "phoneNumber": "+61 400 000 000",
    "utmSource": "google",
    "utmMedium": "cpc",
    "utmCampaign": "brand",
    "utmTerm": null,
    "referrer": "https://www.google.com/",
    "landingPage": "/",
    "device": "desktop",
    "city": "Sydney",
    "country": "AU",
    "region": "NSW",
    "gclid": null,
    "gbraid": null,
    "fbclid": null
  }
]

POST /api/wix/site

Finds or creates the Lead Recorder site record behind a Wix app install, called by the Wix app (not by Zapier or Make) once a user connects their API key during setup. Requires a JSON body with name and domain. Returns the existing site if one with that domain is already linked to the account; otherwise creates one, subject to the account's plan limit on number of sites.

curl -X POST -H "X-Api-Key: lr_xxx" -H "Content-Type: application/json" \
  -d '{"name":"My Website","domain":"example.com"}' \
  https://www.leadrecorder.com/api/wix/site

201 Created
{ "id": "abc123", "snippetKey": "9f2c..." }

New Lead trigger

A polling trigger: once connected, pick a site from the dropdown and Zapier or Make checks for new leads on that site automatically. No webhook setup or extra configuration is needed.

Connecting via Pabbly Connect or n8n

Neither requires a published Lead Recorder app. Both have a generic HTTP action that can call the same endpoints documented above directly.

Pabbly Connect

1. 1Create a workflow and add an API by Pabbly (or generic HTTP) action as the trigger step.
2. 2Set the method to GET, the URL to https://www.leadrecorder.com/api/zapier/leads?siteId=YOUR_SITE_ID, and add a header named X-Api-Key with your Lead Recorder API key.
3. 3Set the workflow to poll on a schedule (every few minutes is typical) and map the returned lead fields into whatever action runs next.

n8n

1. 1Add an HTTP Request node, set to GET, with the URL https://www.leadrecorder.com/api/zapier/leads?siteId=YOUR_SITE_ID.
2. 2Under Authentication, choose Generic Credential Type → Header Auth, with the name X-Api-Key and your Lead Recorder API key as the value.
3. 3Trigger the node on a Schedule Trigger node (polling) or call it from anywhere else in a workflow that needs current lead data.