Campaigns and tracking

Access boundary: Current capability and authority required.

Implemented; role, exact-document and channel gates apply.

Surfaces: Web, REST and MCP; reporting and approval rights are independently checked.

Read the engineering guide · All features

Capabilities

1. Named campaign with CSV recipients
2. Row validation, errors and duplicate detection
3. Prepare individual dispatches with the selected document
4. Dispatch list/detail with prices and statuses
5. Aggregate reporting and usage according to current rights
6. Eligible cancellation and review of uncertain operations
7. Channel/ceiling administration without blind retries
8. Path-scoped browser refresh prevents stale resources or cancelled 401s from replacing a newer session

REST operations

• GET /api/dispatches
• POST /api/dispatches
• GET /api/dispatches/{id}
• POST /api/dispatches/{id}/confirm
• POST /api/dispatches/{id}/cancel
• GET /api/campaigns
• POST /api/campaigns
• GET /api/campaigns/{id}
• POST /api/recipients/validate

Read the REST integration guide for authentication, errors and contract discovery.

MCP tools

• approve_and_send_dispatch
• cancel_dispatch
• confirm_dispatch
• get_dispatch_status
• list_dispatches
• prepare_dispatch
• review_dispatch

Read the MCP integration guide for scope, approval and host boundaries.