API Reference Card
| Detail | Value |
|---|---|
| Base URL | https://{dc}.api.mailchimp.com/3.0/ |
| Auth | API Key via HTTP Basic (anystring:API_KEY) or OAuth 2.0 |
| Rate limits | 10 simultaneous connections |
| Data center | Extract dc from your API key (e.g. us14 from abc123-us14) |
| Mavera base | https://app.mavera.io/api/v1 |
| Mavera auth | Authorization: Bearer mvra_live_... |
All examples use three environment variables:
MAILCHIMP_API_KEY (your full API key including the -dc suffix), MAILCHIMP_DC (data center, e.g. us14), and MAVERA_API_KEY. Python examples use requests with Basic Auth (anystring as username, API key as password); JavaScript examples use fetch with the same pattern.Prerequisites
Mailchimp account with data
You need a Mailchimp account with at least one audience (list) containing subscribers and at least 5 sent campaigns with performance data.
API key
Generate an API key in Mailchimp → Account & Billing → Extras → API keys. The key includes your data center suffix (e.g.
abc123def456-us14).Extract data center
The
dc is the portion after the dash in your API key. For abc123def456-us14, your DC is us14 and your base URL is https://us14.api.mailchimp.com/3.0/.Mavera API key
Get your key from Mavera dashboard.
Jobs
| # | Job | Mailchimp Data | Mavera Surface | Output |
|---|---|---|---|---|
| 1 | Subscriber Segment → Persona Creation | Segments + Members | Custom Personas | Segment-grounded personas |
| 2 | Campaign Performance → Content Optimization | Campaign Reports | Brand Voice | Winning-content-derived brand voice |
| 3 | Email A/B Winner → Focus Group Why | A/B Test Results | Focus Groups | Qualitative A/B explanation |
| 4 | Audience Interest Tags → Content Generation | Interest Categories | Generate | Interest-personalized email content |
| 5 | Re-Engagement Campaign Builder | Inactive Subscribers | Mave Agent + Generate | Multi-step re-engagement sequences |
| 6 | Open Rate Prediction | Historical Campaigns | Focus Groups | Subject line testing with synthetic audience |
Rate Limits & Production Notes
| Mailchimp API | Limit | Strategy |
|---|---|---|
| All endpoints | 10 simultaneous connections | Use sequential requests with 300-500ms delays |
| Members endpoint | 1,000 per page; max 10 concurrent | Paginate with offset; add delays |
| Campaign reports | Same connection pool | Cache results; reports don’t change after send |
| Concern | Recommendation |
|---|---|
| API key security | Mailchimp API keys have full account access. Use OAuth 2.0 for production integrations with scoped permissions. |
| Data center routing | Always extract the dc from your API key. Using the wrong DC returns 403. Format: https://{dc}.api.mailchimp.com/3.0. |
| Batch operations | For creating/updating many subscribers, use Mailchimp’s Batch Operations endpoint instead of individual calls. |
| Webhook vs. polling | For real-time campaign events, use Mailchimp webhooks instead of polling the API. Configure in Audience → Settings → Webhooks. |
| Mavera credits | Monitor at Dashboard. Job 6 (open rate prediction) with 4 personas × 4 questions is credit-intensive. |
| List hygiene | Job 5 identifies inactive subscribers. After re-engagement attempts, clean unresponsive addresses to maintain deliverability. |
What’s Next
All Integrations
50+ API integrations with full code
Mailchimp API Docs
Official Mailchimp Marketing API reference
Personas API
Full reference for POST /api/v1/personas
Focus Groups API
Full reference for POST /api/v1/focus-groups
Brand Voice API
Full reference for POST /api/v1/brand-voices
Generate API
Full reference for POST /api/v1/generations