Prepare a Loops domain and transactional template

Loops transactional email is API-triggered content created in its editor or imported template workflow. Prepare that content before integrating code: the sending request selects a transactional email ID and provides the variables it expects.

Establish the template contract

1. Authenticate the sending domain using the dashboard’s current DNS instructions.
2. Create the transactional email and its required data variables.
3. Review/publish or otherwise activate it according to the current editor workflow and record its actual transactional ID.
4. Create/store an API credential on the backend, separate from frontend analytics or public configuration.

Use Loops’ transactional documentation. Variables in body, links, and supported headers need deliberate values; an empty production reset URL is not an acceptable test of the template.

Keep transactional and audience state separate

Loops documents that a transactional recipient need not already belong to the marketing Audience, and transactional sending does not automatically mean marketing enrollment. Do not set addToAudience as an incidental side effect without consent/product requirements.

Unsubscribed marketing contacts may still receive requested transactional messages. That is not permission to label promotions as transactional. Loops also documents that transactional emails do not track opens or clicks, so do not make those signals a delivery acceptance test.

Verify the template with safe variable values and a controlled recipient before wiring real login or purchase events. MailKite templates and credentials are separate resources if you later migrate.