Suppressions & Consent

Suppressions prevent email from being sent to specific recipients. Consent records track the legal basis for contacting someone. Both are enforced automatically by the policy engine.

Suppression scopes

Suppressions can be applied at three levels:

Scope	Description
`global`	Blocked across all tenants. Checked first.
`tenant`	Blocked for a specific tenant.
`campaign`	Blocked for a specific campaign only.

When evaluating a send request, global suppressions are checked first, then tenant, then campaign.

Add a suppression

POST https://api.molted.email/v1/suppressions

curl

curl -X POST https://api.molted.email/v1/suppressions \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "tenantId": "tenant_abc123",
    "email": "user@example.com",
    "scope": "tenant",
    "reasonCode": "manual_dnc"
  }'

Field	Type	Required	Description
`tenantId`	`string`	Yes	Your tenant identifier.
`email`	`string`	Yes	Email address to suppress.
`scope`	`string`	Yes	Suppression scope: `global`, `tenant`, or `campaign`.
`reasonCode`	`string`	Yes	Reason for suppression.

Reason codes

Code	Description
`complaint`	Recipient marked an email as spam.
`hard_bounce`	Email address hard-bounced.
`manual_dnc`	Manually added to do-not-contact list.
`legal_request`	Suppressed due to a legal request (e.g., GDPR erasure).
`role_account`	Role account (e.g., `info@`, `admin@`) that should not receive automated email.

Remove a suppression

DELETE https://api.molted.email/v1/suppressions/:id

curl

curl -X DELETE https://api.molted.email/v1/suppressions/SUPPRESSION_ID \
  -H "Authorization: Bearer YOUR_API_KEY"

List suppressions

GET https://api.molted.email/v1/suppressions

curl

curl "https://api.molted.email/v1/suppressions?tenantId=tenant_abc123&email=user@example.com" \
  -H "Authorization: Bearer YOUR_API_KEY"

Parameter	Type	Required	Description
`tenantId`	`string`	Yes	Your tenant identifier.
`email`	`string`	No	Filter by email address.

Consent records document the legal basis for contacting someone. They support GDPR and other privacy regulation compliance.

POST https://api.molted.email/v1/consent

curl

curl -X POST https://api.molted.email/v1/consent \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "tenantId": "tenant_abc123",
    "email": "user@example.com",
    "basis": "explicit_opt_in",
    "jurisdiction": "EU"
  }'

Legal bases

Basis	Description
`explicit_opt_in`	The recipient explicitly opted in to receive email.
`legitimate_interest`	Sending is justified by a legitimate business interest.
`contractual`	Email is necessary for fulfilling a contract.
`legal_obligation`	Email is required by law.

GET https://api.molted.email/v1/consent

curl

curl "https://api.molted.email/v1/consent?tenantId=tenant_abc123&email=user@example.com" \
  -H "Authorization: Bearer YOUR_API_KEY"

On this page