Form endpoint defined.
A form endpoint is the URL an HTML form submits to, the address in the form's action attribute that receives the browser's POST and processes the submitted fields.
How a form endpoint works
Every form needs somewhere to send its data. When a visitor hits submit, the browser gathers the named fields and POSTs them to one URL, the endpoint. Whatever lives at that address decides what happens next: validate the fields, store them, send an email, trigger an automation.
Traditionally the endpoint was a script you hosted yourself, a PHP handler or a serverless function you wrote and maintained. A hosted form endpoint replaces that: you point the form's action at a service's URL, and the service does the processing. FormWire's endpoint is https://api.formwire.com/submit. It accepts the encodings browsers actually send (form-encoded and multipart) plus JSON for fetch calls, and one endpoint serves every form you run: a public access key in the form tells it which account and form the submission belongs to.
More than an address.
Accepts what browsers send
Form-encoded and multipart submissions work as-is, and the same URL takes JSON from fetch, one endpoint for plain HTML and for JavaScript.
Answers honestly
A clear success response when the submission lands, and a JSON error message on validation failure that you can show the visitor.
Fronts the whole pipeline
Behind the URL sit spam filtering, durable storage, email delivery and integrations. The endpoint is just the front door.
Related questions
It's one specific kind of API: a single URL with one job (accept a form submission via POST). You don't need API documentation to use it; a plain HTML form tag with the right action attribute is a complete client.
How the form action attribute aims the POST →Yes. With FormWire every form on every site you run POSTs to the same URL, and the access key field in each form routes the submission to the right place. You never mint a new endpoint per form.
The endpoint rejects it with an HTTP 4xx status and a JSON body explaining why (a missing required field, for instance). Fetch-based forms can show that message to the visitor directly.
Everything between the POST and your inbox: spam checks, durable storage, email delivery with retries, and fan-out to integrations. The endpoint is the visible tip of the feature set.
See everything FormWire runs behind one endpoint →Want to see it working?
Read the docsPoint your form at an endpoint that does the rest.
Free tier forever. No credit card required.