Form webhooks

Select a Form block in the KuikPage editor. Under New submissions set a Webhook URL and, if you like, Email me each one. Every submission is stored in the dashboard's Submissions list regardless. Form webhooks are included from the PRO plan.

PayloadCopy Anchor Link

{
  "event": "form.submission",
  "page": { "id": "pg_...", "url": "https://yourbrand.kuik.page" },
  "blockId": "f8a2...",
  "formTitle": "Request a quote",
  "submittedAt": "2026-09-06T14:02:11.482Z",
  "country": "US",
  "data": {
    "Name": "Ada Lovelace",
    "Email": "ada@example.com",
    "Message": "Two pallets, please.",
    "Consent": true
  }
}

data is keyed by the labels you gave the fields, so a Zapier zap or a CRM mapping reads naturally. The endpoint rules are the same as for scan webhooks: https, public hostname.

Form deliveries ride the same queue as scan webhooks: at least once, retried up to five times on timeouts, 429s and 5xx answers (30 seconds, 2 minutes, 10 minutes, then an hour), and listed with their status under GET /webhooks/deliveries with eventType form.submission. Every attempt carries the same X-KuikCode-Delivery header; deduplicate on it if a slow success is followed by a retry. Retries read the block's current Webhook URL from the published page, so clearing it or unpublishing the page stops them.

Form webhooks are not signed, because the URL lives on the Form block rather than on a workspace endpoint with a secret. Use a secret path segment in your URL if you need to reject strangers.

Submissions are also available through GET /submissions in the API.