Connecting a form to your own backend

Forms are built and validated but not connected. You point them at your own endpoint, which is a one-time setup step.

This is the most common surprise, so it is worth being blunt: templates with a form do not store or send anything out of the box.

The form is complete on the visitor's side. It validates input, shows errors properly, and has a real success state. What it does not have is somewhere to send the data, because that would mean tying you to one provider.

What you do

Point the form at an endpoint you control. Depending on the template that is an attribute on the form, such as:

<form data-booking data-endpoint="https://example.com/api/bookings">

The template posts JSON to that address and treats any 2xx response as success. Where it goes is your choice: a form backend service, an email service, a spreadsheet, or your own server.

What has to live on your side

Anything security or reliability related belongs in your endpoint, not in the page:

• Checking availability or stock before accepting a submission
• Rate limiting and spam handling
• Authentication
• Sending confirmation emails

Client-side validation in the template is there for usability. It is not a security boundary, and it never can be.

Still stuck? Email [email protected] and say which template and what you expected to happen.