Send email

​

Endpoint

POST https://api.pocketsflow.com/newsletters/send

​

Request body

​

Example request

curl https://api.pocketsflow.com/newsletters/send \
  -H "Authorization: Bearer pk_live_xxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "to": ["customer@example.com"],
    "subject": "Your weekly update",
    "html": "<p>Hi there — here is what is new this week.</p>",
    "fromName": "Acme Studio",
    "replyTo": "hello@acme.com"
  }'

# Up to 100 recipients in a single call
curl https://api.pocketsflow.com/newsletters/send \
  -H "Authorization: Bearer pk_live_xxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "to": ["a@example.com", "b@example.com", "c@example.com"],
    "subject": "Doors are open",
    "text": "The cohort is live — reply if you have any questions.",
    "preview": "Your spot is ready"
  }'

​

Example response

{
  "id": "665f1c2e8b3735856be339aa",
  "accepted": ["customer@example.com"],
  "status": "sent"
}

​

Errors

​

Behavior & limits

• Recipients: provide a single address or an array of 1–100. Addresses are normalized to lowercase and de-duplicated before sending. More than 100 returns 400.
• Body: provide html, text, or both. If only text is given, a simple HTML body is generated from it; text is always used as the plain-text alternative for better deliverability.
• Sender identity: fromName and replyTo default to your Newsletter settings when omitted. The sending address must be a verified sender.
• Compliance: every email automatically includes your footer, physical address, and a per-recipient unsubscribe link — you don’t add these yourself.
• Recording & usage: each send is stored as a post (source: api) and counts toward your email usage (totalEmailsSent).
• Idempotency: the endpoint does not de-duplicate across separate calls — guard against accidental double-sends on your side (for example, key retries on your own request id).

​

Notes

• This endpoint shares the /newsletters surface; to publish a full newsletter post to all subscribers instead, use POST /newsletters/posts/{id}/send.
• The full OpenAPI definition is available in the interactive API reference.

​

Related topics

• API reference
• MCP server — call this as the send_email tool.