Email campaigns are the central workflow in Monterey. A campaign combines a template, a recipient source (MSSQL query or CSV upload), optional A/B variants, and scheduling configuration.Documentation Index
Fetch the complete documentation index at: https://docs.montereyfinancial.dev/llms.txt
Use this file to discover all available pages before exploring further.
Campaign CRUD
| Operation | Endpoint |
|---|---|
| List campaigns | GET /email-campaigns/ |
| Get campaign | GET /email-campaigns/{id} |
| Create | POST /email-campaigns/ |
| Update | PUT /email-campaigns/{id} |
| Delete | DELETE /email-campaigns/{id} |
| Toggle active | PATCH /email-campaigns/{id}/active |
Sending a campaign
Trigger a campaign send with:- Queries MSSQL for recipients based on the campaign’s configured query
- Suppresses bounced email addresses from the historical bounce list
- Syncs the template to Campaigner
- Generates an IFUR file for MegaSys automation
- Uploads via MegaSys and creates a campaign run with recipient logs
Dry run
Add?dry_run=true to test the send pipeline without actually dispatching emails:
CSV recipients
For campaigns using uploaded CSV files instead of MSSQL queries:| Endpoint | Purpose |
|---|---|
POST /email-campaigns/csv/parse | Parse a CSV file, returns columns and a preview |
POST /email-campaigns/{id}/csv/upload | Attach a CSV file to a campaign |

