A form endpoint is the specific URL you put in a form's action attribute - the address every submission is sent to. When a visitor submits the form, their browser performs an HTTP POST to this endpoint, and the form backend behind it receives the data, runs validation and spam checks, stores it, and triggers any notifications or webhooks you have configured.
Each form usually has its own endpoint, so submissions are kept separate and you can apply per-form rules: which fields are required, what counts as spam, where notifications go, and how long data is retained. Because the contract is just "POST to this URL," a form endpoint works the same whether your form is hand-written HTML, generated by a framework, or built in a no-code tool.
Keeping field name attributes stable once an endpoint is live matters, because those names are the keys your notifications, exports, and webhooks rely on. The forms guide covers embedding an endpoint in any stack.
Related terms
Form backend
A hosted service that receives, processes, and stores HTML form submissions so your website does not need its own server-side code.
Webhook
An automated HTTP POST that a service sends to a URL you control whenever an event happens, so your systems react in near real time without polling.
Jamstack form
A form on a Jamstack (statically generated, JavaScript-enhanced) site that posts to a hosted form backend instead of a server of its own.
Read the full guide