Documentation

FormToInbox documentation

The free builder exports portable files. Read the generated comments before changing action URLs or scripts.

HTML form action

For a self-hosted form, replace the placeholder action with an endpoint you control. Use HTTPS and validate every field again on the server.

JavaScript and JSON

The standard export uses native form submission. If you later use fetch or JSON, configure the receiving endpoint explicitly and never assume browser validation is sufficient.

CORS and allowed domains

A hosted endpoint should allow only configured origins where possible, reject unexpected methods and avoid reflecting arbitrary origins with credentials.

Errors and rate limits

A future hosted API will use stable machine-readable errors, request-size limits and endpoint/IP rate limits. Exact production limits are not published until the service is active.

Quick integration examples

<form action="https://your-endpoint.example/submit" method="post">
  <label for="email">Email</label>
  <input id="email" name="email" type="email" required>
  <button type="submit">Send</button>
</form>

Replace the placeholder with a destination you control. Never expose API secrets in browser code.

Global privacy
Necessary storage

Keeps your form-builder draft and privacy choice on this device.

Always on
Sale or targeted-ad sharing

FormToInbox does not sell personal information or share it for cross-context behavioural advertising.

Off