Form Endpoint API — One POST URL for Any HTML Form

A form endpoint is a single URL you POST your form data to instead of writing server-side code to handle it. With splitforms, that URL is https://splitforms.com/api/submit: point any HTML form's action attribute at it, add your access_key as a hidden field, and splitforms stores the submission, filters spam, and emails you — the browser does the rest.

How a Form Endpoint Works

1. You register a form and receive an access key that identifies your account and form.
2. You add the endpoint URL to your form's action attribute, along with the access key as a hidden field.
3. A visitor submits the form — their browser sends a standard HTTP POST to the endpoint.
4. The endpoint processes the submission: validates, filters spam, stores in a database, sends email notifications, and fires webhooks.
5. You see the submission in your dashboard and inbox within seconds.

Minimal Form Endpoint Example

<form action="https://splitforms.com/api/submit" method="POST">
  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
  <input name="name" type="text" placeholder="Name" required>
  <input name="email" type="email" placeholder="Email" required>
  <textarea name="message" placeholder="Message" required></textarea>
  <button type="submit">Send</button>
</form>

That's it. No SDK, no server, no API route, no database configuration. The endpoint handles everything.

How to Connect a Form to a Form Endpoint

1. Get your free access key — Sign up at splitforms.com/login. Every form gets its own access key on the Free plan — 500 submissions/month, unlimited forms, no credit card.
2. Point your form's action at the endpoint — Set action="https://splitforms.com/api/submit" and method="POST" on your <form> tag, then add access_key as a hidden field with your key as the value.
3. Add the honeypot field — Include a hidden botcheck input that must stay empty. Bots fill every field, including hidden ones; humans never see it. Any submission where it's filled in gets rejected.
4. Add the time-trap field — Add a hidden form_loaded_at field set to a timestamp when the page loads. splitforms uses the gap between load and submit to catch instant bot fills.
5. Set optional control fields — Add subject for a custom notification email subject, redirect for a post-submit thank-you URL, or replyto to set the reply-to address — no code required for any of them.
6. Submit a test entry and check your dashboard — Fill out the form yourself. The submission appears in your splitforms dashboard and inbox within seconds — email notifications are free on every plan.

What the Endpoint Does for You

Form Endpoint vs. Building Your Own

Using the Endpoint with Different Frameworks

Plain HTML

<form action="https://splitforms.com/api/submit" method="POST">
  <input type="hidden" name="access_key" value="YOUR_KEY">
  <input name="email" type="email" required>
  <button>Send</button>
</form>

Full walkthrough with the honeypot field and styling: see the HTML contact form guide.

React / Next.js (fetch)

const res = await fetch("https://splitforms.com/api/submit", {
  method: "POST",
  body: formData, // new FormData(formElement)
});

Framework-specific examples: React and Next.js, or browse every framework guide.

cURL

curl -X POST https://splitforms.com/api/submit \
  -H "Content-Type: application/json" \
  -d '{"access_key":"YOUR_KEY","name":"Test","email":"test@test.com","message":"Hello"}'

Reading Submissions Back Out

The endpoint isn't one-way. Once submissions land, pull them back out with GET https://splitforms.com/api/submissions, sent with an Authorization: Bearer <token> header — find your token at Dashboard → MCP. Filter by form (id or access key), page through results with limit (default 25, max 100), before, and since, and read the response as { submissions, has_more }. It's capped at 60 requests/minute. Full parameter list in the API reference.

The same token powers the free splitforms MCP server, so AI agents and coding tools can create forms and list submissions with built-in tools instead of you hand-rolling the integration. Prefer push over pull? Route new submissions to Slack, Discord, or any URL with a signed webhook instead of polling the endpoint.

FAQ

Questions? Email hello@splitforms.com