BootForm

Appearance

Getting started ​

BootForm is a form backend: point an HTML <form> at a BootForm endpoint and it starts accepting submissions immediately - no account, no signup, no API call before your first real submission arrives.

Zero-friction quick start ​

Pick any ID (a UUID works well) and POST to it - nothing to register first:

html
<form action="https://f.bootform.com/{form_id}" method="POST">
  <input name="email" type="email" required />
  <textarea name="message"></textarea>
  <button type="submit">Send</button>
</form>

The first submission to a given {form_id} creates that form automatically. Submissions are held (up to 10 per form) until someone claims it - see below - so you can try this out right now without losing what comes in while you decide whether to sign up.

Requests can be application/x-www-form-urlencoded, multipart/form-data (for file uploads), or application/json. On success, BootForm redirects back to the page that submitted the form; add _format=json (or send Accept: application/json) to get a 200 {"ok":true} JSON response instead, for AJAX/fetch submissions.

Claiming a form ​

You don't need to go find the claim URL yourself - every submission to a form nobody's claimed yet already points at it. A classic browser POST redirects the visitor straight to https://app.bootform.com/claim/{form_id} once the submission is held; an AJAX/JSON request gets the same URL back in the response body instead, as {"ok":true,"status":"pending_claim","claim_url":"https://app.bootform.com/claim/{form_id}"}, so you can surface it in your own UI while you're testing the integration.

Either way, create a BootForm account (or log into an existing one) and follow that link to take ownership of the form. Once claimed, it behaves like any other form in your dashboard: full submission history, notification destinations, spam protection, and every other setting described in the rest of this documentation.

How the pieces fit together ​

  • f.bootform.com is the public submission endpoint - where your <form>'s action points. No authentication; this is the one part of BootForm meant to be hit directly by a visitor's browser.
  • app.bootform.com is the dashboard - where you view submissions, configure notifications, and manage your account, forms, and workspaces.
  • api.bootform.com is the REST API behind that dashboard - the same operations, callable directly with an API key. See The API.
  • mcp.bootform.com is the MCP (Model Context Protocol) server - lets an AI agent create and configure forms, read submissions, and manage notification destinations on your behalf. See MCP & AI Agents.

Where to go next ​