Email

Trimite email-uri tranzacționale către adrese pe care contul tău le-a verificat, folosind aceeași cheie de integrare care alimentează notificările tale push. Destinatarii confirmă printr-un link de dublă acceptare înainte de a putea primi email-uri.

How it works

1. Register a recipient. The account owner adds an address to the verified list. PushWard sends that address a one-time confirmation link (valid for 48 hours).
2. The recipient confirms. Clicking the link verifies the address. Only confirmed, non-unsubscribed addresses become sendable — and only for the account that verified them (verification is per-account, never shared).
3. Your integrations send. Call POST /emails to deliver transactional mail to a verified recipient, using the same integration key that powers your push notifications. Recipients can one-click unsubscribe at any time, and hard bounces or spam complaints suppress an address automatically.

Authentication

Send an Email

curl -X POST https://api.pushward.app/emails \
  -H "Authorization: Bearer hlk_YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "[email protected]",
    "subject": "Nightly backup complete",
    "text_body": "All 4 repositories backed up in 12m 30s.",
    "html_body": "<p>All <strong>4</strong> repositories backed up in 12m 30s.</p>"
  }'

{
  "id": 42,
  "to": "[email protected]",
  "subject": "Nightly backup complete",
  "status": "sent",
  "provider_message_id": "0100018f3a2b...",
  "created_at": "2026-06-09T02:00:00Z",
  "delivery": "all"
}

Recipients & History

Recipient management — registering an address, sending its double-opt-in confirmation, listing recipients, resending a confirmation, and removing one — is handled in the PushWard app, not through the public API. You curate the verified list in the app; your integration keys can only send to addresses already confirmed there.

Your send history — every email this account has sent or attempted — is likewise viewable in the app's Email tab, including each message's delivery status: sent, bounced, complained, failed, or suppressed (updated asynchronously as the delivery provider reports bounces and complaints).

Verification & Deliverability

• Double opt-in. Confirmation links are single-use and expire after 48 hours; the app can resend a fresh one to a still-pending address.
• One-click unsubscribe. Every email automatically carries the RFC 8058 one-click unsubscribe headers and a link — you don't add anything. An unsubscribe is per-account: it stops mail from your account to that address, and you can re-register the address (with a new confirmation) later.
• Automatic suppression. A hard bounce or spam complaint suppresses the address globally and immediately — subsequent sends are silently skipped and logged as suppressed. This protects sender reputation for everyone on the relay.
• Recipient cap. Each account can keep up to 50 verified recipients. See Limits.

Errors

Email errors use the same RFC 9457 Problem Details body shape and stable code values as the rest of the API.