Outbox
One row per outbound message, from draft to engagement, on one status ladder — and the approve call that is the only way a draft ever sends.
The Outbox is the one outbound record: one row per message, addressed to one
person, from creation through delivery to engagement. Every row sits on one
status ladder — draft → sent → opened / clicked / replied, with held,
bounced, failed and declined as the named side exits. Rows group by the
run_id of the campaign run that wrote them.
Read the drafts a run left you
List outbox — GET /api/v1/outbox
curl "https://moabcrm.com/api/v1/outbox?status=draft" \
-H "Authorization: Bearer $DASH_API_KEY" \
-H "Project-ID: pr_zest"Show me the draft messages from the last rundata_query {
"collection": "outbox",
"where": {
"status": "draft"
}
}{
"object": "list",
"data": [
{
"object": "outbox",
"id": "obj_123",
"subject": "Hermes joins the team",
"body": "Hi Dana — saw Riverside just opened a second pit…",
"status": "draft",
"sent_at": "2026-07-25T12:00:00.000Z",
"sent_via": "resend",
"opened_at": "2026-07-25T12:00:00.000Z",
"clicked_at": "2026-07-25T12:00:00.000Z",
"status_reason": "status reason",
"status_detail": "status detail",
"copy_gap": "copy gap",
"channel": "email",
"content_type": "content type",
"employee_id": "employee_123",
"from": "from",
"to": "dana@riversideenv.com",
"recipient_company_domain": "recipient company domain",
"reason": "reason",
"followup": true,
"step_number": 1,
"total_steps": 1,
"scheduled_for": "2026-07-25T12:00:00.000Z",
"review_context": {
"company_summary": "company summary",
"company_stage": "company stage",
"company_category": "company category",
"person_name": "person name",
"person_title": "person title",
"persona_reason": "persona reason",
"content_angle": "content angle",
"message_summary": "message summary",
"why_this_company": "why this company",
"why_this_person": "why this person",
"why_this_message": "why this message",
"checks": [],
"review_signal": "review signal"
},
"created_at": "2026-07-25T12:00:00.000Z",
"updated_at": "2026-07-25T12:00:00.000Z"
}
],
"has_more": false,
"next_cursor": null
}Filter by agent_id and status; the reference page
(outbox) lists every field, filter and sort key.
Rows carry a timeline.
Approve one
curl --fail-with-body "https://moabcrm.com/api/v1/outbox/$DRAFT_ID/approve" \
-H "Authorization: Bearer $MOAB_API_KEY" \
-H "Project-ID: $PROJECT_ID" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: acme-outbox.approve-1' \
-d '{}'Approve is what the product's Approve chip does, and it is the only road to
a send: the draft is released to its connected provider, and the row reaches
sent only on provider evidence — sent_at, sent_via and external_id
land together. A row that stays held is visible backlog with a named
status_reason, never a silent success. Declining is the same action row
with the Decline press: nothing sends and the decline lands on the row's
timeline.
What the ladder means
- You only ever write
draft. Delivery and engagement rungs (sent,opened,clicked,replied,bounced,failed) are written by the server on provider evidence, never by a model or a client. sentmeans a provider confirmed this message. A campaign going live with a row preloaded is not evidence anybody received anything.- The project's run mode bounds every send. In
sandboxthe recipient is rewritten onto the sandbox audience; inlivea send still needs the agent to be live — see Turn it live and Channels & Sending.
A refusal — an action you lack the role for, or a send the gate stops — is always named on the row's timeline rather than lost in a log; see Control plane.
Next: Channels & Sending — how an approved message ships.