Form ingest

Form ingest is the channel that turns a browser form submission into a Hooksbase event. Every webhook exposes a public form URL of the form https://hooks.hooksbase.com/v1/form/{publicId}, returned as formIngestUrl when the webhook is created.

The endpoint handles three methods: POST to submit, GET to render a minimal built-in HTML form useful for testing or a lightweight embed, and OPTIONS for CORS preflight so a form can live on another origin.

The credential is the URL

There is no signing secret and no API key on the form route. The unguessable publicId in the URL is the entire access control, so treat the URL as sensitive and rotate the webhook if it is exposed. A form submission should not be treated as coming from a verified source — unlike a provider pack webhook, there is no signature to check.

Payload shape

Standard form encodings produce flat key-value data, plus a files array for multipart submissions. That shape rarely matches what a consumer wants, so most teams add a payload transform or Automation to restructure the submission before delivery.

Same pipeline as every other channel

A form submission becomes a normal delivery: retried under the webhook's retry policy, recorded in delivery history, replayable, and routed to the destination the routing rules select.

See Form to webhook for the full channel overview.