Embedding a Form

Every published form has a public route such as /f/event-registration. Respondents never need an Amen account, and the route receives no Identity, Core or product-session token.

Hosted link

The hosted page is the launch-safe integration. Copy its URL from the builder or download the QR code in PNG or SVG for WhatsApp, a printed sheet or a projection screen.

<a href="https://forms.example/f/event-registration">Register</a>

The public service resolves only the immutable published schema. Draft content, church members and previous responses are never part of the public representation.

Iframe boundary

Automatic iframe resizing is planned but not shipped. When it is added, the integration must:

• accept messages only from the exact configured Forms origin;
• validate a small versioned message schema;
• send only height and completion events;
• never put bearer tokens, submission values or member data in postMessage;
• allow each church to restrict the parent origins that may embed its form.

Until that contract exists, use the hosted link instead of copying the schema into another product.

Page and Link

Amen Page and Amen Link will store an opaque public form reference. They must not duplicate the questions. Forms remains responsible for the live published version, validation, consent snapshot and submission lifecycle.

Public submission

The public client supplies an idempotency key. The server validates all values again against the published version, commits the submission and its outbox event in one transaction, and returns the same successful-looking response for flagged spam.