API & Webhooks

API

There is no API key a customer can create. Dashboard endpoints (forms, leads, export) require a logged-in session cookie and are for the LeadFormHub app. The lead submission endpoint is public so a published form can accept responses. It is not a general customer REST API.

• Submit lead (public): POST https://leadformhub.com/api/leads/submit — send formId and data (field values). Optional: utm (object with utm_source, utm_medium, utm_campaign, utm_term, utm_content), referrerUrl, landingPageUrl for lead source tracking.
• Forms: List, create, get, update, update schema, delete — under /api/forms.
• Leads: List, get one, delete, export (CSV/Excel) — under /api/leads.
• Support: Create and list support requests, get thread, post replies — under /api/support-requests. Staff can post replies with Authorization: Bearer <SUPPORT_API_KEY>.

Full request/response shapes, authentication details, and error codes are in the API & Webhooks documentation (docs/API-AND-WEBHOOKS.md in the repository).

Webhooks

Outbound lead webhooks

On the Business plan, the workspace owner or an admin can save a URL in Integrations. LeadFormHub POSTs lead.created, lead.stage_changed, and lead.won to that URL. An optional secret signs the body with HMAC. Free and Pro cannot create outbound webhooks.

Inbound support email

This is a platform endpoint for recording support-ticket replies. It is not a customer integration.

Configure your email provider (SendGrid, Mailgun) to POST to this URL. See Raise Support Request and the repo doc docs/support-inbound-email.md for setup steps.