Form basics

Form backend

A form backend is a service that receives what a website form submits, then validates it, stores it, filters spam and sends it on to email, a spreadsheet or another tool.

Also called: form handler, form endpoint, forms as a service, form API

An HTML form can collect what a visitor types, but it cannot do anything with it. When the visitor presses submit, the browser sends the data to a URL, and something at that URL has to be listening. That something is the form backend.

What a form backend does

  • Receives the submission at an endpoint (a URL the form posts to).
  • Validates it: required fields, email addresses, file types and sizes.
  • Filters spam before it reaches you.
  • Stores the submission so it can be searched and exported later.
  • Delivers it: an email notification, a Slack message, a row in a spreadsheet, a webhook to your own system.
  • Reports what happened, including which deliveries failed.

Why static sites need one

A static site is a folder of files with no code running per request, so there is nothing to receive a submission. You can run your own server with mail sending and spam handling, which is real work to build and keep secure, or point the form at a hosted form backend and keep the site static.

What to compare

Look at spam protection, what happens when a delivery fails, where data is stored and which agreement covers it (data residency and the data processing agreement), whether you can send to the tools you use, and how submissions are limited or priced.

In StaticForm

You create a form in the dashboard and get an endpoint of the form https://api.staticform.app/api/v1/forms/YOUR_FORM_ID. Set it as the form’s action and every submission is validated, spam-scored, stored and passed to the submit actions you configured: email, webhooks, Slack, Discord, Microsoft Teams, Google Sheets and Notion. Submissions are unlimited on every plan, and each action execution is logged so you can see and retry failures.

Learn more