Email consent records with MailSlurp

When sending transactional or promotional email, make sure each recipient has given the permission required for that message. When MailSlurp consent is required before sending to an external address, the recipient must explicitly opt in through a double opt-in email verification.

What is double opt-in consent?

Double opt-in confirms that a recipient controls the address and wants to receive your email. The recipient submits an email address, receives a confirmation link, and follows that link before you send further messages. This extra confirmation protects the recipient, your sending reputation, and the reliability of future delivery.

Info. If you are sending to domains that you control for testing, contact support to have the test domain approved for sending.

The MailSlurp consent process

1. The recipient opens the consent form at https://api.mailslurp.com/opt-in/:userId, with :userId replaced by the MailSlurp user ID.
2. The recipient enters an email address, confirms the consent checkbox, and submits the form.
3. MailSlurp sends a confirmation link to that address.
4. The recipient follows the link to confirm the opt-in.
5. The recipient can revoke consent later at https://api.mailslurp.com/opt-out/:userId.

Why is this necessary?

Consent requirements vary by recipient and message type, but permission is also a practical delivery signal. Double opt-in gives you a record of confirmation, reduces unwanted mail, and lowers the chance of bounces, rejections, and complaints. The result is a healthier sending workflow and a better experience for the people receiving your email.

What are my options?

For more control, collect the recipient's permission in your own opt-in form and use the MailSlurp ConsentController API to send the verification link. After the recipient confirms, your application can send email to that verified address.