Security and spam protection

Origin checks, Turnstile, honeypot, rate limits and public API data boundaries.

The public API is unauthenticated by design. It accepts only form submissions and never exposes stored submissions or configuration.

Origin allowlist

Each website has an exact canonical origin allowlist. CORS returns only the exact allowed origin and Vary: Origin. Credentials are not allowed. Origin: null and unlisted origins are rejected. Origin is not authentication and must not be treated as a secret.

Turnstile

Turnstile is verified server-side with Cloudflare Siteverify. Postvia checks success, expected hostname, expected action where configured, and token freshness. Tokens are single use. An outage fails closed with retryable 503.

Honeypot

The optional _honeypot field must remain empty. A populated value returns a generic 403 verification_failed and never stores the payload.

Rate limits

Layered per-IP, per-form and global limits are enforced in Redis. The limiter fails closed if it cannot establish a decision.

Data boundaries

  • No public endpoint returns submissions, recipients or configuration.
  • Client-supplied recipients, headers, redirects and webhook destinations are never honoured.
  • Payloads are encrypted at rest.
  • Request bodies and tokens are not logged.
  • Error responses expose safe codes, field messages and a request ID only.

Interactive testing

The documentation’s API playground is read-only in production because the docs origin is not on customer allowlists. Do not weaken CORS to enable a hosted playground. Use the copyable examples or test from the customer website.