如何批量获取Mailchimp会员活动？避免单会员单次API调用

Great question—dealing with 28k individual API calls is definitely a pain, and Mailchimp does offer better ways to batch this work instead of hitting their endpoint for every single subscriber. Let’s break down the most efficient options tailored to your needs:

1. 使用Mailchimp Batch Operations API（首选） #

This is exactly designed for your scenario: it lets you bundle up to 1000 individual API requests into a single batch call. For your 28k subscribers, that means only 28 total requests instead of 28k—huge efficiency gain.

Here’s how to implement it:

• Construct a JSON payload where each entry in the operations array represents a single request to fetch a subscriber’s activity. Each operation needs:
  • method: GET
  • path: /lists/{your_list_id}/members/{subscriber_hash}/activity (replace placeholders with your actual values)
  • operation_id: A unique identifier (like the subscriber’s email hash) so you can map results back to specific users later
• Send this payload to the Batch API endpoint: POST /batches
• Mailchimp processes the batch asynchronously. Poll the batch status via GET /batches/{batch_id} until it’s marked as finished
• Once complete, you’ll get a URL to download a JSON file with all results, including success/error status and activity data for each subscriber

Example snippet of a batch payload:

{
  "operations": [
    {
      "method": "GET",
      "path": "/lists/abc123/members/xyz789/activity",
      "operation_id": "subscriber_1"
    },
    {
      "method": "GET",
      "path": "/lists/abc123/members/def456/activity",
      "operation_id": "subscriber_2"
    }
  ]
}

2. 使用Export API批量导出带活动数据的会员列表 #

If you just need a one-time dump of all historical subscriber activity, the Export API is even simpler. It lets you pull a CSV or JSON file of your entire list, including activity fields directly in the export.

• Call the export endpoint: GET /export/lists/{your_list_id}
• Use the fields parameter to explicitly request activity-related data (e.g., fields=email_address,activity). This will include each subscriber’s open/click history, unsubscribes, and other actions right alongside their profile data.

Note: The exact fields available depend on your Mailchimp plan, but most paid plans support exporting full activity history with subscriber profiles.

3. 关于List Activity API为空的说明 #

You mentioned the List Activity API returned empty results—just to clarify: the /lists/{list_id}/activity endpoint returns aggregate list-level metrics (like total opens/clicks over time), not individual subscriber activity. That’s why it wasn’t useful for your use case. If you ever need aggregate data, double-check that your list has existing activity (new lists might not) and that you’re using the correct list ID.

4. 长期方案：设置Webhooks实时接收活动数据 #

For ongoing tracking (instead of one-time historical pulls), set up a Mailchimp Webhook. This way, Mailchimp will send a POST request to your server whenever a subscriber takes an action (opens, clicks, unsubscribes, etc.). You won’t need to poll for data at all—just store the events as they come in. This is perfect for keeping your activity data up-to-date without repeated API calls.

关键注意事项 #

• Rate Limits: Even with batch requests, Mailchimp enforces limits (e.g., 10 batch requests per minute for paid plans). Throttle your submissions to avoid hitting these.
• Batch Processing Time: Large batches can take a few minutes to process—use a 30-60 second polling interval to avoid unnecessary requests.
• Error Handling: Some requests in a batch might fail (e.g., invalid subscriber hash). The batch results will include error details, so you can retry those individually if needed.

内容的提问来源于stack exchange，提问作者Tasty