SheetLink Forms beta

Form endpoint

Definition

A form endpoint is the URL that receives a form's data when someone submits it. The browser (or your JavaScript) sends an HTTP POST request to that address, and whatever lives there is responsible for parsing the payload and doing something with it.

Endpoints typically accept a few encodings: application/x-www-form-urlencoded (the default for HTML forms), application/json (common for fetch and AJAX submissions), and multipart/form-data (used when forms include files). A well-behaved endpoint also answers differently depending on who is asking: a plain HTML submission expects to be redirected to a next page, while a JavaScript caller expects a machine-readable response it can act on inline, showing a success message without leaving the page.

Because the endpoint URL is wired into your markup, stability matters. A good endpoint is permanent - you should be able to publish a form once and never revisit the URL, even as settings, destinations, and spam rules change behind it.

How SheetLink Forms uses it

In SheetLink Forms, every form gets a permanent endpoint of the shape https://sheetlinkforms.com/f/{token}. It accepts POST as urlencoded, JSON, or multipart (file parts are dropped currently), with a 256KB body cap. Plain HTML submissions get a 303 redirect to a hosted thank-you page or your own redirect URL; JSON and AJAX callers get {"ok":true,"id":"..."} back. Behind the endpoint, submissions are screened for spam and delivered as rows to Google Sheets or Excel Online.

Response codes, encodings, and examples are documented in the developer docs, and the live demo posts to a real endpoint you can inspect.

Related terms: Form backend · Form action · CORS · Webhook