Introduction
Postvia receives form submissions, stores them durably and delivers them to configured recipients.
Postvia is a private form-processing service for managed customer websites. A website posts a form to Postvia; Postvia validates it, stores it durably and delivers it to one or more configured recipients through a transactional email provider.
You do not need a backend on the customer website. You do need:
- A Postvia form with a public ID.
- An allowed origin for the customer website.
- At least one verified recipient and a ready Turnstile configuration.
What a success response means
A 201 response means the submission, delivery intent and outbox rows were committed in one database transaction. It does not mean the email has reached an inbox. Delivery happens asynchronously and is at-least-once; an ambiguous provider outcome can produce a duplicate.
The public API is unauthenticated by design. The public ID identifies a form; it is not an authentication secret. Origin allowlists, Turnstile and rate limits protect the endpoint.
Choose a path
- How Postvia works — the request and delivery pipelines.
- Create your first customer and website — the operator workflow.
- Submit your first JSON request — the smallest working request.
- API reference — the complete public contract.