Campaign Monitor · Rate Limits
Campaignmonitor Rate Limits
Rate limiting for the Campaign Monitor API. Campaign Monitor limits only its /transactional endpoints and does not publish the numeric ceiling — it publishes the runtime signal instead (three X-RateLimit-* response headers and a 429), which is what an agent actually needs. The rest of the REST surface carries no published limit. Volume ceilings that DO bite in practice are per-operation batch caps and plan-level send caps, recorded below.
Campaignmonitor Rate Limits is the machine-readable rate-limit profile for Campaign Monitor on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 2 rate-limit definitions.
Tagged areas include Email Marketing, Campaigns, Subscribers, Transactional Email, and Segments.
2 Limits
Email MarketingCampaignsSubscribersTransactional EmailSegmentsNewslettersAutomationMarketing AutomationWebhookEmail DeliverabilityMarketing
Limits
Transactional endpoint rate limit per API key / OAuth token
Exceeding the limit returns HTTP 429 with the body {"Code": 429, "Message": "Rate limit exceeded"}. Clients should back off for X-RateLimit-Reset seconds.
Standard REST endpoints
No documented hard limit. The rate-limit headers are documented only in the context of /transactional. Absence of a published limit is not a guarantee of no limit.