curl --request POST \
  --url https://brew.new/api/v1/sends \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "test": true,
  "emailId": "eml_welcome",
  "subject": "Welcome to Brew",
  "to": "qa@acme.com"
}
'

{
  "status": "sent",
  "recipient": "qa@acme.com"
}

Emails

Send an email

Sends an email design. Polymorphic on the test flag:

test: true → a synchronous one-off TEST delivery of the design’s current (or pinned) body to a single address. Forces the Brew default sender (no verified domain needed), targets one to address, and never creates a Send row. Returns 200 { status: "sent", recipient }.
default / test: false → a campaign send combining the design (emailId, optionally pinned to emailVersionId), a verified domainId, and a target — a saved audienceId OR inline to (a single email or an array, max 50) — into one delivery event. The same design can be sent unlimited times; every call mints a new send. Returns 202 { sendId, runId } — poll via GET /v1/analytics/sends?sendId=.

Campaign target — provide EXACTLY ONE of audienceId or to. Inline recipients face the same unsubscribe/suppression gate and per-recipient quota as audience sends. For per-recipient event-driven delivery, publish an automation and fire its trigger (POST /v1/automations/triggers/{triggerEventId}/fire).

Brand scoping: resources (emailId, domainId, audienceId) living in a different brand surface as 404 so the API never confirms cross-brand existence.

POST

sends

curl --request POST \
  --url https://brew.new/api/v1/sends \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "test": true,
  "emailId": "eml_welcome",
  "subject": "Welcome to Brew",
  "to": "qa@acme.com"
}
'

{
  "status": "sent",
  "recipient": "qa@acme.com"
}

Authorizations

Authorization

string

header

default:Bearer brew_your_api_key

required

Send your Brew API key as Authorization: Bearer brew_xxx.

Headers

Idempotency-Key

string

Optional idempotency key for safe retries. Reusing the same key with the same request body returns the original response for 24 hours.

Required string length: 1 - 100

Body

application/json

Option 1
Option 2

test

enum<boolean>

required

Available options:

true

emailId

string

required

Minimum string length: 1

subject

string

required

Minimum string length: 1

string<email>

required

emailVersionId

string

Minimum string length: 1

previewText

string

Maximum string length: 50

replyTo

string<email>

Response

The TEST send (test: true) was delivered synchronously to the single recipient.

status

enum<string>

required

Available options:

sent

recipient

string<email>

required

Accessibility audit Cancel a send

⌘I