Your handler expects one event per request
How you'll know: After an import, contacts are missing in your CRM.
Fix: Events arrive batched, up to 1,000 per request, in an Events array with the ListID. Loop through every event, not just the first.
Campaign Monitor, now part of Marigold, still runs its API on the old createsend domain: https://api.createsend.com/api/v3.3/. Almost every call needs one of two IDs, a Client ID for the account and a List ID for the subscriber list, and the two aren't interchangeable.
Auth: send your API key as the username in HTTP Basic auth, with a blank or dummy password. For an app other people connect, Campaign Monitor prefers OAuth, sent as a bearer token.
Client ID: your profile image, then Account settings, then API keys. Or call GET /clients.json.
List ID: open the list, click Settings on the left and scroll to the bottom for the List API ID. Or call GET /clients/{clientid}/lists.json.
Outside the transactional endpoints, the API answers in XML by default. Add .json to the route or send Accept: application/json, and send request bodies in the same format.
POST /subscribers/{listid}.json with EmailAddress, Name, CustomFields as an array of Key and Value pairs, and ConsentToTrack set to Yes, No or Unchanged.
Watch for: leaving out ConsentToTrack returns error 214. Custom field values are capped at 250 characters, and dates should be sent as yyyy/mm/dd.
With Resubscribe: true, someone who unsubscribed, went inactive or is on the suppression list is added back. Campaign Monitor's docs ask you to use that with caution. Most syncs from a CRM should leave it false.
POST /subscribers/{listid}/import.json takes up to 1,000 subscribers per call. Split larger loads, or you'll get error 209.
POST /lists/{listid}/webhooks.json with Events (any of Subscribe, Update, Deactivate), your Url and a PayloadFormat of json or xml. Fire a test payload with GET /lists/{listid}/webhooks/{webhookid}/test.json.
How you'll know: After an import, contacts are missing in your CRM.
Fix: Events arrive batched, up to 1,000 per request, in an Events array with the ListID. Loop through every event, not just the first.
How you'll know: Nothing has arrived for days, and the webhook shows as inactive.
Fix: Campaign Monitor deactivates a webhook after sustained errors for more than a week. Fix the endpoint, then reactivate it with PUT /lists/{listid}/webhooks/{webhookid}/activate.json.
How you'll know: People who left the list are still marked as subscribed elsewhere.
Fix: Subscribe to Deactivate. It fires for unsubscribes, spam complaints, hard bounces and people set inactive, so it's the one event your CRM needs most.
How you'll know: Form signups don't show up until much later, or at all.
Fix: On confirmed opt-in lists, Subscribe only fires when the person clicks the verification link. That's by design, not a bug.
How you'll know: Order emails bounce back with Rate limit exceeded.
Fix: Rate limits apply to the /transactional endpoints. Read X-RateLimit-Remaining and X-RateLimit-Reset on each response and wait out the window.
Zapier, HubSpot and Google Sheets connectors already cover plenty of common Campaign Monitor jobs, and the Salesforce integration has its own page. They're the right start when the fields line up and the trigger you need is on their list.
A direct build makes sense when the data comes from your own app or database, when custom fields need mapping or conditions, or when Deactivate events have to change a record somewhere else within minutes. n-frames builds those integrations against the Campaign Monitor API, including the webhook listener that answers fast, handles batches and records consent.
Building for your own account, an API key is simpler. Building something other businesses install, use OAuth and plan for token refresh from the start.
The identifier for a client account in Campaign Monitor. Many calls are scoped to it, such as listing that client's subscriber lists. Find it under Account settings and API keys, or with GET /clients.json. The List ID is the other one you'll need, for anything about a specific list.
Yes, per subscriber list. You can subscribe to Subscribe, Update and Deactivate events, choose JSON or XML payloads, and test, activate, deactivate or delete each webhook through the Lists API.
Yes, through existing connectors, which generally cover basic list and subscriber sync. Custom field mapping, conditions, or a trigger those connectors don't offer needs a direct integration with the API.
There's no separate API fee that we know of, but you need an active Campaign Monitor account, and sends made through the API count against that account's plan and limits.
Yes, through its /transactional endpoints, separate from marketing campaigns. Those endpoints are JSON only and are the ones with rate limits, so build in backoff for order confirmations and account notices.