Response format

Success responses, idempotent replay and native HTML redirects.

Created

HTTP/1.1 201 Created
Content-Type: application/json
Cache-Control: no-store, private
X-Request-Id: 01JY8Z3K4M5N6P7Q8R9S0T1V2W
{
  "success": true,
  "submission_id": "8f2c1e7a4b6d8c0e5f3a2b1c9d8e7f60",
  "message": "Your enquiry has been received."
}

submission_id is an opaque receipt. Treat it as an identifier, not a secret. The submission is durably stored and scheduled; the email has not necessarily reached an inbox.

Idempotent replay

An identical replay returns 200 OK with the same submission_id. No new submission, delivery or notification is created.

Native HTML redirect

A native HTML submission receives 303 See Other with a Location header pointing to the form’s validated success URL or the hosted thank-you page.

Error responses

{
  "success": false,
  "error": {
    "code": "validation_failed",
    "message": "Check the submitted fields.",
    "fields": {
      "email": ["Invalid email address."]
    }
  },
  "request_id": "01JY8Z3K4M5N6P7Q8R9S0T1V2W"
}

fields is present only for field validation errors. All public responses are Cache-Control: no-store, private. Safe internal details, stack traces, recipients and configuration are never returned.

Request IDs

Use request_id or the X-Request-Id header when contacting support. It is a ULID and contains no payload data.