# BootForm

BootForm is a zero-friction form backend: point an HTML `<form>` at a BootForm endpoint and it
starts accepting submissions immediately — no account, no signup, no API call needed before your
first real submission arrives. Claim the form later (create an account, or link an existing one)
to see submissions in a dashboard and configure notifications. Free plan covers common use; paid
plans raise quotas and unlock features (see https://bootform.com/pricing).

Full API reference: https://bootform.com/openapi.json (OpenAPI 3.0, auto-generated from the real
API, not hand-maintained) and https://bootform.com/llms-full.txt (the same surface, condensed for
LLM consumption).

## Quick start (zero-friction submission)

Pick any UUID (or let a client library generate one) and POST to it — no pre-registration:

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

Any `{form_id}` works the first time it's POSTed to. The submission is held (up to 10 submissions,
per form) until someone claims it by creating a BootForm account and visiting
`https://app.bootform.com/claim/{form_id}` — from then on it's a normal, owned form.

Requests may be `application/x-www-form-urlencoded`, `application/json`, or (once file uploads
ship) `multipart/form-data`. Success: redirect back to the referring page (or a `200 {"ok":true}`
JSON body for AJAX/`Accept: application/json` requests).

## Special field names (stripped before storage, never appear as a submitted field)

| Field | Effect |
|---|---|
| `_redirect` (or `_next`) | Redirect the browser here after a successful submission |
| `_replyto` | Sets the notification email's Reply-To header |
| `_subject` | Overrides the notification email's subject line |
| `_format=json` | Forces a JSON response even for a classic (non-AJAX) browser POST |
| `_honeypot` | Spam trap — leave empty; a bot that fills it in gets silently dropped as spam |

A hidden `_honeypot` input (off-screen, `autocomplete="off"`) is included automatically in every
BootForm-generated HTML snippet.

## Notification channels — what's real today

Only **email** and **Discord** actually deliver notifications right now. The API accepts other
destination types (`webhook`, `slack`, `telegram`) but their delivery isn't implemented yet — don't
configure them expecting output.

## REST API

Base URL for account/dashboard operations: `https://api.bootform.com`. Auth:
`Authorization: Bearer {api_key}` (create a key at `https://app.bootform.com` → API Keys, or via
the MCP tool below). Resources: forms, submissions, notification destinations, verified sender
emails, workspaces, account. Full detail: https://bootform.com/llms-full.txt or
https://bootform.com/openapi.json.

## MCP (Model Context Protocol) server

An AI agent can create and configure BootForm forms directly, without visiting the dashboard.

- **Endpoint:** `https://mcp.bootform.com/sse`
- **Auth:** an account API key, either as `Authorization: Bearer {api_key}` or `?api_key={api_key}`
  in the connection URL (some MCP clients can't set custom headers on an SSE connection).
- **Tools:** `bootform_create_form`, `bootform_configure_form`, `bootform_list_forms`,
  `bootform_get_snippet`, `bootform_add_email`, `bootform_add_discord`.

Full tool schemas: https://bootform.com/llms-full.txt.

## Links

- Marketing / docs: https://bootform.com
- Dashboard: https://app.bootform.com
- Submission endpoint: https://f.bootform.com/{form_id}
- Dashboard API: https://api.bootform.com
- MCP server: https://mcp.bootform.com/sse
- Full API reference: https://bootform.com/openapi.json
- Full LLM-optimized reference: https://bootform.com/llms-full.txt