How do APIs expose engagement data?

If your ESP has an API (most do), it can give your systems access to the same engagement data you see in the dashboard, plus often more. Instead of you logging in to export a CSV, your code asks the API and gets the data back in a structured format.

What ESP APIs typically expose

Campaign-level stats: delivery rate, open rate, click rate, bounce rate, unsubscribe count. Subscriber-level data: each contact's event history, what they opened, what they clicked, when they last engaged. Event logs: individual timestamped events per recipient. Some ESPs expose all of this. Others restrict certain data types by plan tier.

How the API request works (non-technical version)

An API is a way for software systems to talk to each other over the web. Your system sends a request to the ESP's server saying "give me the engagement stats for campaign ID 12345." The ESP sends back the data in a structured format (usually JSON), which your system then reads and uses. Authentication happens through an API key, a secret credential you generate in your ESP account settings.

Pulling data this way is useful for building custom dashboards, syncing engagement data to your CRM without manual exports, or running analysis that your ESP's native reporting doesn't support.

API vs. webhooks

There are two ways to get event data from your ESP. APIs are pull-based: your system asks for data when it needs it, on a schedule or on demand. Webhooks are push-based: the ESP sends data to your system the moment an event happens. For real-time use cases (immediate bounce suppression, instant complaint handling), webhooks are faster. For batch reporting and analysis, API polling works fine.

Most major ESPs (Mailchimp, Klaviyo, Brevo, SendGrid) have well-documented REST APIs. If you're not a developer, this is a conversation for your engineering team. If you are, check your ESP's API reference for authentication setup and rate limits before building anything.