Skip to content

Capture surface

Email capture API

Anything that does not fit a form: a checkout, a booking confirmation, a partner integration, your own bespoke flow.

What it records

  • Supported context fields your server sends
  • The form the capture came through
  • The consent the person gave
  • The request ID returned and stored with consent events

Supported fields are recorded from the payload your server sends. Unsupported keys or values are rejected; we assert nothing you did not send.

Setting it up

Post captures to the public endpoint — it needs no key, because it is the same endpoint your forms use, and it is rate limited per form. Use a scoped key in Settings for the separate server-side operations your integration needs.

Setup docs: add a signup form to a website · capture emails from an API · signup provenance fields · double opt-in and suppression.

Other surfaces