[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Campaign Monitor API

> Every Campaign Monitor endpoint on Cotlet: inputs, JSON Schema, cURL, Python and Node.js examples and an example response for each call.

Source: https://cotlet.dev/docs/api/campaign-monitor

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

13 endpoints for Campaign Monitor, each at its own method and path, called with your API key. Open an endpoint for its inputs, examples and response.

- Base URL: `https://cotlet.dev/api/v1/campaign-monitor`
- Connects with: Your own Campaign Monitor login with the permissions the job needs (reports, create campaigns, automation). You sign in in your own Cloud Browser and keep your multi-factor authentication.
- Integration page: https://cotlet.dev/integrations/campaign-monitor-api-mcp-server

## Read

Return data and change nothing in the account.

| Endpoint | Description |
|---|---|
| [`GET /lists`](https://cotlet.dev/docs/api/campaign-monitor/list_lists.md) | Returns the subscriber lists of the account. |
| [`GET /segments`](https://cotlet.dev/docs/api/campaign-monitor/list_segments.md) | Lists the segments of one list, or of all lists. |
| [`GET /lists/{list_id}/subscribers`](https://cotlet.dev/docs/api/campaign-monitor/list_subscribers.md) | Lists the subscribers of a list by state. |
| [`GET /campaigns`](https://cotlet.dev/docs/api/campaign-monitor/list_campaigns.md) | Lists sent, scheduled or draft campaigns. |
| [`GET /campaigns/{campaign_id}/report`](https://cotlet.dev/docs/api/campaign-monitor/get_campaign_report.md) | Reads the Snapshot of a sent campaign. |
| [`GET /campaign-activities`](https://cotlet.dev/docs/api/campaign-monitor/list_campaign_activity.md) | Lists recipients of a sent campaign by what they did. |
| [`GET /journeys`](https://cotlet.dev/docs/api/campaign-monitor/list_journeys.md) | Lists the journeys of the account. |
| [`GET /journeys/{journey_id}`](https://cotlet.dev/docs/api/campaign-monitor/get_journey.md) | Reads the summary and email steps of a journey. |

## Write

Change the account. Calls marked Confirm wait for the user to approve them.

| Endpoint | Description |
|---|---|
| [`POST /campaigns/{campaign_id}/segment-from-campaigns`](https://cotlet.dev/docs/api/campaign-monitor/create_segment_from_campaign.md) | Creates a segment of people who opened, clicked or did not open a campaign. |
| [`POST /campaign-drafts`](https://cotlet.dev/docs/api/campaign-monitor/create_campaign_draft.md) | Creates a single campaign in Drafts with subject, sender, recipients and HTML. |
| [`POST /lists/{list_id}/subscribers`](https://cotlet.dev/docs/api/campaign-monitor/add_subscriber.md) (Confirm) | Adds one person to a list. |
| [`POST /campaigns/{campaign_id}/schedule`](https://cotlet.dev/docs/api/campaign-monitor/schedule_campaign.md) (Confirm) | Sends a draft now or schedules it for later. |
| [`PUT /journeys/{journey_id}/status`](https://cotlet.dev/docs/api/campaign-monitor/set_journey_status.md) (Confirm) | Moves the on and off switch of a journey. |

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.