Documentation

1. Create an access key

Sign in, create a form, and copy its access key. Each account can create up to five forms in this early version.

2. Paste this HTML

<form action="https://formqivo.com/submit" method="POST">
  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
  <input name="name" required placeholder="Your name">
  <input type="email" name="email" required placeholder="Email">
  <textarea name="message" required></textarea>
  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
  <button type="submit">Send message</button>
</form>

3. Verify delivery

Use Send test submission in your dashboard, then check your inbox. Recent submissions shows the last 30 delivery records (without storing message content).

JSON API

POST /api/submit with Content-Type: application/json. Include access_key plus your fields. A success response looks like {"success":true,"message":"Message sent successfully."}.

Validation failures return HTTP 400, rate-limit responses return HTTP 429 and delivery errors return HTTP 503. Use the HTTP status and the success property, not only the message text.

Limits and behavior

Maximum 16 KB request body, 30 fields, 10,000 characters of form data and 50 submissions per form per hour, 60 submissions per account per rolling 24 hours and 100 submissions across this early-access service per rolling 24 hours. Invalid keys and excessive requests are throttled. Access keys are public identifiers, not private authorization secrets: anyone who knows the key can submit to that form. Rotate a key if it is being abused, then update your website. The system does not store submitted message content in the database.

JavaScript cross-origin POST supports JSON requests. Native HTML form submissions navigate to the API JSON response; use JavaScript to show an inline success message if desired. File uploads, attachments and custom redirect URLs are not supported.