FormsFort

Options Reference

FormsFort options reference for Web3Forms-compatible hidden fields, reserved names, captcha tokens, uploads, redirects, and paid/manual gates.

Options Reference

Any non-reserved input name is forwarded as submitted data. Reserved names below control routing, email behavior, redirects, spam checks, uploads, captcha, and integrations.

Routing

OptionDescription
access_keyRequired public form key for POST /submit.
apikeyLegacy alias for access_key.
POST /submit/YOUR_ACCESS_KEYPath variant when hidden fields are not available.

Email

OptionDescription
emailSubmitter email. Used as reply-to when the form reply-to mode allows it.
subjectNotification subject override. Blank values are ignored.
from_nameNotification display-name override. New forms default to Notifications.
replytoExplicit per-submit reply-to address override.
reply-to modeDashboard setting for submitted email, default address, or no reply-to.
ccemailPaid/manual comma- or semicolon-separated CC recipients.

Flow and Spam

OptionDescription
redirectPer-submit success redirect for non-JavaScript posts. Overrides the form redirect default.
redirect defaultDashboard setting used when an HTML post does not include redirect.
botcheckHidden honeypot. Filled values reject as spam; JSON false-like values are accepted.
allowed domainsDashboard setting that restricts browser submissions to exact hostnames.

Files, Captcha, and Integrations

OptionDescription
attachmentPaid/manual file upload field for multipart forms.
data-advancedAdvanced uploader file-input attribute handled by the client helper script.
data-fileuploadLegacy Web3Forms uploader placeholder or file-input attribute.
recaptcha_responseGoogle reCAPTCHA v3 token.
h-captcha-responsehCaptcha token.
cf-turnstile-responseCloudflare Turnstile token.
webhookPaid/manual per-submit webhook URL.

Common hidden fields

<form action="https://api.formsfort.dev/submit" method="POST">
  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
  <input type="hidden" name="subject" value="New website lead" />
  <input type="hidden" name="from_name" value="Example Site" />
  <input type="hidden" name="replyto" value="support@example.com" />
  <input type="hidden" name="redirect" value="https://example.com/thanks" />
  <input type="checkbox" name="botcheck" style="display:none" />
</form>

Paid/manual options

<input type="hidden" name="ccemail" value="sales@example.com; ops@example.com" />
<input type="hidden" name="webhook" value="https://example.com/formsfort" />
<input type="file" name="attachment" />

<input
  type="file"
  name="attachment"
  data-advanced="true"
  multiple
  data-max-files="3"
  data-max-file-size="5MB"
/>

<!-- Legacy placeholder markup is also supported. -->
<input type="hidden" data-fileupload="true" data-max-files="3" />
<script src="https://api.formsfort.dev/client/script.js" async defer></script>

Captcha token names

reCAPTCHA v3: recaptcha_response
hCaptcha: h-captcha-response
Cloudflare Turnstile: cf-turnstile-response

Forwarding rules

FormsFort forwards custom fields to email, autoresponder copies, Google Sheets, native notifications, and generic webhooks. Reserved routing fields, captcha tokens, honeypots, access keys, and attachment content are excluded from generic webhook payloads.

  • Repeated browser field names are joined as comma-separated values.
  • Blank subject, from_name, and replyto values do not replace safe defaults.
  • Dashboard reply-to mode decides whether submitted email, a default address, or no reply-to is used.
  • Per-submit redirect values override the form redirect default.
  • Server-side submissions require a paid/manual IP safelist.
  • JavaScript requests should handle JSON instead of relying on redirect.

On this page