Skip to main content
Two kinds of “options” apply to a Formpaste form: fields you put directly in the <form> that get read by /submit, and per-form config you set once in the dashboard. This page is the complete list of both.

Reserved fields (in the form body)

These field names are read by /submit itself - set them as inputs in your form (or keys in your JSON/FormData body). Every other field name is yours.
Only access_key is required. The other three are opt-in - add botcheck and _ts to strengthen spam detection, add redirect only for no-JS forms that need a post-submit navigation.

Per-form config (dashboard)

These aren’t submitted with each request - you set them once per form, from that form’s Setup tab in the dashboard (or via the MCP create_form tool for the initial destination email). They control how a form behaves for every submission it receives.
There’s no config endpoint to call - these are dashboard-only settings. The MCP server doesn’t expose an update_form tool; if you need to change one of these after create_form, do it in the dashboard. See MCP server.

Free vs. Pro fields

Attempting to set a Pro-gated field (additional_recipients, cc_recipients, autoresponder_enabled, webhook_url) on a Free-plan form fails at save time:

Error reference

Every /submit error code, HTTP status, and meaning.

Your first form

The dashboard walkthrough these options come from.