Campaign Monitor API

Name: Campaign Monitor API
Brand: Campaign Monitor API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingEmail Marketingbasic, oauth272 EndpointsREST

For Agents

Manage email-marketing clients, lists, subscribers, campaigns, segments, templates, journeys, and transactional sends through a multi-tenant agency-friendly API.

Install Jentic One Beta

Connect the Campaign Monitor API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Campaign Monitor API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Campaign Monitor API.

Create and send draft email campaigns from /campaigns/{clientid}.json and /campaigns/{campaignid}/send.json

Manage subscriber lists, segments, and webhooks per client across an agency portfolio

Retrieve recipient activity and bounce reports for sent campaigns via /campaigns/{campaignid}/recipients.json and /bounces.json

GET STARTED

Start building with Campaign Monitor API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Campaign Monitor API for, with concrete tasks.

★ Agency Multi-Client Campaign Management

Marketing agencies running campaigns on behalf of many brands need a single API surface to create client workspaces, manage their lists, and dispatch campaigns. Campaign Monitor's client-scoped routes (/clients.json, /clients/{clientid}/lists.json, /campaigns/{clientid}.json) keep each brand's data isolated while letting the agency operate centrally.

Call POST /clients.json to onboard 'Acme Corp', create a list under that client via the Lists endpoints, then POST /campaigns/{clientid}.json to draft a launch announcement.

Automated Campaign Send and Reporting

Marketing-ops teams want to schedule a campaign, broadcast it, and feed bounce and engagement data back into a CRM. The Campaign Monitor API exposes /campaigns/{campaignid}/send.json for dispatch and /campaigns/{campaignid}/recipients.json plus /bounces.json for downstream reporting in a single integration.

POST /campaigns/{campaignid}/send.json to dispatch a campaign, then poll /campaigns/{campaignid}/bounces.json hourly and write each bounce to the CRM contact record.

Subscriber Hygiene and Compliance

Compliance workflows need to suppress unsubscribed or complained addresses across all of a client's lists. /clients/{clientid}/suppress.json adds addresses to the client-wide suppression list and /unsuppress.json reverses the action when a user re-opts in, helping keep deliverability scores high.

POST /clients/{clientid}/suppress.json with the email address from a complaint webhook to block future sends to that address.

AI Agent Email Workflows via Jentic

Through Jentic, an agent searches for 'send an email campaign', loads the input schema for /campaigns/{campaignid}/send.json, and executes the dispatch without managing Basic Auth or OAuth tokens directly. Jentic's vault stores the API key or OAuth token so it never enters the agent's prompt context.

Use the Jentic SDK to search 'send an email campaign', load the /campaigns/{campaignid}/send.json operation, and execute it with the campaign ID returned from a draft creation step.

Key Endpoints

72 endpoints — jentic publishes the only available openapi specification for campaign monitor api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/clients.json

Create a client workspace

POST

/campaigns/{clientid}.json

Create a draft campaign for a client

POST

/campaigns/{campaignid}/send.json

Send a draft campaign

GET

/campaigns/{campaignid}/recipients.json

List campaign recipients

GET

/campaigns/{campaignid}/bounces.json

List campaign bounces

GET

/clients/{clientid}/lists.json

List subscriber lists for a client

POST

/clients/{clientid}/suppress.json

Suppress email addresses for a client

POST

/clients.json

Create a client workspace

POST

/campaigns/{clientid}.json

Create a draft campaign for a client

POST

/campaigns/{campaignid}/send.json

Send a draft campaign

GET

/campaigns/{campaignid}/recipients.json

List campaign recipients

GET

/campaigns/{campaignid}/bounces.json

List campaign bounces

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Campaign Monitor API keys or OAuth tokens are stored encrypted in the Jentic vault. Agents receive scoped execution rights and Jentic injects the credential into the Authorization header at call time, so the raw secret never enters the agent's context.

Intent-based discovery

Agents search by intent (for example, 'send an email campaign') and Jentic returns the matching Campaign Monitor operation along with its input schema, so the agent can call /campaigns/{campaignid}/send.json without browsing the Campaign Monitor docs.

Time to first call

Direct Campaign Monitor integration: 2-3 days for OAuth setup, multi-client routing, and bounce-handling logic. Through Jentic: under two hours to search, load, and execute.

FAQs

Specific to using Campaign Monitor API through Jentic.

Why is there no official OpenAPI spec for Campaign Monitor API?

Campaign Monitor does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Campaign Monitor API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Campaign Monitor API use?

It supports HTTP Basic auth (API key as username, any value as password) or OAuth 2.0 authorization-code flow against https://api.createsend.com/oauth. Through Jentic, either credential type is held in the Jentic vault and injected at execution time so it never enters the agent's prompt context.

Can I send a campaign through Jentic?

Yes. Search 'send an email campaign' through the Jentic SDK. Jentic returns POST /campaigns/{campaignid}/send.json with its input schema. Provide the campaign ID from a prior draft creation and execute the operation to dispatch the campaign.

How do I retrieve the bounce report for a sent campaign?

Call GET /campaigns/{campaignid}/bounces.json with the campaign ID. The response paginates through hard and soft bounces, which you can then write to a CRM or suppression list using POST /clients/{clientid}/suppress.json.

Does the API support multiple client workspaces under one agency account?

Yes. Use POST /clients.json to create a client workspace and the /clients/{clientid}/* routes (lists, segments, campaigns, suppression) to manage that client's data in isolation while the agency operates from a single account.

Are transactional emails available through this API?

Yes. The Transactional resource exposes endpoints for sending transactional messages outside of broadcast campaigns. Use them when an email is triggered by a user action rather than scheduled to a list.

Campaign Monitor API

Connect the Campaign Monitor API to your agent

Capabilities

Start building with Campaign Monitor API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs