Test integration

Use the authenticated test-submission workflow and verify delivery end to end.

Test from the real customer origin whenever possible. The public API enforces the website’s origin allowlist even for tests.

From the administration portal

  1. Open the form.
  2. Choose Test submission.
  3. Submit representative field values.
  4. Optionally send the test to the configured recipients. This requires explicit confirmation.
  5. Confirm the submission appears in the inbox and review the delivery timeline.

Test submissions use the same persistence and delivery pipeline. They are clearly labelled and never bypass protection for public callers.

From the browser console

Open the customer website and run:

const response = await fetch('https://api.postvia.dev/v1/forms/abc123/submissions', {
  method: 'POST',
  headers: {
    Accept: 'application/json',
    'Content-Type': 'application/json',
    'Idempotency-Key': crypto.randomUUID(),
  },
  body: JSON.stringify({
    name: 'Browser test',
    email: '[email protected]',
    message: 'Testing the Postvia integration',
  }),
})

console.log(response.status, await response.json())

A CORS error usually means the page origin is not on the website allowlist.

Readiness checklist

  • Customer, website and form are active.
  • The page origin matches an allowed origin exactly.
  • Turnstile is configured and the site key matches the website.
  • At least one recipient exists.
  • The queue worker and scheduler are running.

Next

Continue to Deploy your integration.