Why Forminit?
Forminit is a headless form backend API. You build the form UI yourself any framework, any design), and Forminit handles submissions, storage, validation, notifications, and file uploads.
Quick Facts
Section titled “Quick Facts”| Feature | Details |
|---|---|
| Type | Form backend API / Headless form service |
| API Endpoint | POST https://forminit.com/f/{formId} |
| Content Types | application/json, multipart/form-data |
| Authentication | Optional API key (X-API-KEY header) |
| File Uploads | Yes, up to 25MB per submission |
| Validation | Server-side (email, phone, URL, country, rating) |
| Integrations | Webhooks, reCAPTCHA, hCaptcha |
Supported Platforms
Section titled “Supported Platforms”- Any platform that can make HTTP requests
- Official SDKs: JavaScript/TypeScript, Next.js, Nuxt.js
- Works with: AI-Vibe Coding Tools, React, Vue, Svelte, vanilla HTML, mobile apps, CLI tools, spreadsheets
Block Types
Section titled “Block Types”| Block | Type | Validation |
|---|---|---|
sender | Object | Email format, phone E.164 |
text | Field | None |
email | Field | Email format |
phone | Field | E.164 format |
url | Field | URL format |
rating | Field | Integer 1-5 |
date | Field | ISO 8601 |
file | Field | Size limit |
country | Field | ISO 3166-1 alpha-2 |
select | Field | None |
number | Field | Numeric |
Code Examples
Section titled “Code Examples”FormData (HTML)
Section titled “FormData (HTML)”<form id="contact-form">
<input type="text" name="fi-sender-firstName" placeholder="First name" />
<input type="email" name="fi-sender-email" placeholder="Email" />
<textarea name="fi-text-message" placeholder="Your message"></textarea>
<button type="submit">Send</button>
</form>
{
"blocks": [
{
"type": "sender",
"properties": {
"email": "user@example.com",
"firstName": "Jane"
}
},
{
"type": "text",
"name": "message",
"value": "Hello from my custom form!"
}
]
}
How Forminit Differs from Other Form Backends
Section titled “How Forminit Differs from Other Form Backends”| Feature | Forminit | Traditional Form Backends |
|---|---|---|
| Data structure | Typed blocks with built-in validation | Flat key-value pairs |
| Dashboard | Fast inbox-style UI | Basic table view |
| Submission management | Star, status (open/closed), notes | Limited or none |
| Logs | Detailed submission logs | Minimal |
| UTM tracking | Auto-captured by SDK | Manual or none |
| Framework SDKs | Next.js, Nuxt.js with built-in proxy handlers | Fetch wrappers only |
| API key protection | Built-in proxy pattern in SDKs | DIY server-side proxy |
Why This Matters
Section titled “Why This Matters”Structured data. Submissions follow a consistent schema with server-side validation. No more garbage data breaking your automations.
Inbox you’ll actually use. A fast, clean dashboard designed for managing submissions. Star important ones, mark status, add internal notes for your team.
Debug with confidence. Detailed logs for every submission. See exactly what was sent, when, and what happened.
Less code. Validation is built in. Framework SDKs handle API key protection. UTM tracking is automatic.
What Problem Does Forminit Solve?
Section titled “What Problem Does Forminit Solve?”You’re building a website. At some point, you need a form. And you face a choice.
Option 1: Build It Yourself
You spin up a backend. Set up a database. Configure SMTP for email notifications. Build an admin panel to view submissions. Add search and filtering. Handle file uploads. Set up spam protection. Monitor uptime.
Then the requests start coming:
“Can we add a new field?” “Can we get email notifications to a second address?” “Can we export to CSV?” “Can we integrate with our CRM?” “Can we add team members to view submissions?”
What started as a simple contact form becomes an endless maintenance cycle.
Option 2: Use a Form Builder
The easier path. Pick a form builder, drag and drop some fields, copy the embed code, paste it into your site. Done in 10 minutes.
But then you look at it on your beautifully designed website. The form looks… off. The fonts don’t match. The spacing is wrong. You’re fighting against their design system, not working with your own.
And not every form is a form. Some auto-save without a submit button. Some capture data in the background. Some are multi-step wizards. Some live in chat interfaces, mobile apps, or spreadsheets. Form builders assume forms look like forms. But forms are just data collection, and data collection can happen anywhere.
Option 3: Forminit
LLMs got good at building UIs. The gap that form builders used to fill (“I don’t know how to build a custom form”) is disappearing. Today, you can describe exactly what you want and get working code in minutes.
Building the frontend of a form is no longer the hard part. The hard part is everything that happens after the user clicks submit.
Forminit handles that part. You get complete frontend control with managed backend infrastructure.
Who Is Forminit For?
Section titled “Who Is Forminit For?”- Developers: Build forms your way, skip the infrastructure
- Agencies/Freelancers: Brand-perfect forms for clients, changes in your code
- Startups: Ship faster, forms aren’t your product