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"],
  "skipped": ["unsubscribed@example.com"],
  "skippedCount": 1,
  "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).

​

Deliverability protection

• Bounced and spam-reporting addresses are skipped. An address that hard-bounced, or whose owner marked an email from any Pocketsflow creator as spam, is never emailed again. It comes back in skipped, isn’t sent and isn’t charged. On your own list the contact’s status becomes bounced or complained.
• New senders have a daily limit. For the first 14 days, and until your account has sent 1,000 emails, you can send up to 1,000 emails per day (00:00 to 00:00 UTC) across the API, campaigns, automations and test sends. Over the limit, the request is refused with 429 and code: "DAILY_SEND_LIMIT", and nothing is sent.
• High bounce or complaint rates pause sending. Once your account has sent enough email for the numbers to mean something (500 or more in the last 30 days), a hard-bounce rate above 5% or a spam-complaint rate above 0.3% (the limit Gmail and Yahoo set for bulk senders) pauses email sending on your account. Every send is then refused with 403 and error: "EMAIL_SENDING_PAUSED", and scheduled posts go back to draft. Only email is paused: your store, checkout and payouts keep working. We email you when this happens; contact support to get sending again.

{
  "error": "EMAIL_SENDING_PAUSED",
  "code": "EMAIL_SENDING_PAUSED",
  "message": "Email sending on your account is paused while we review recent bounces and spam reports. Your store, checkout and payouts are not affected. Contact support and we'll help you get sending again."
}

​

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.