Skip to main content
Use the @bijection/connectors/mailchimp entrypoint to declare Mailchimp resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Audience members

pull: Anchored since_last_changed walk with signed webhook hints

The following example matches configuration webhooks.

Configuration: standard

Case: mailchimp/members/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: mailchimp. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: members
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: webhooks

Case: mailchimp/members/pull/webhooks. Connection and resource configuration are declared by this exact case. Credential kind: mailchimp. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: members
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Audiences

pull: Whole anchored walk by creation time

The following example matches configuration standard.

Configuration: standard

Case: mailchimp/lists/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: mailchimp. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: lists
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Campaigns

pull: Whole anchored walk by creation time

The following example matches configuration standard.

Configuration: standard

Case: mailchimp/campaigns/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: mailchimp. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: campaigns
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The connection’s server setup (us6, the API key’s suffix) selects https://<server>.api.mailchimp.com; the mailchimp credential is the key (Basic or bearer) or an OAuth token. Identity is the API root’s account_id. Ten simultaneous requests per user are allowed; a 429 states no documented wait. Mailchimp pages by count and offset and states no cursor, so every walk is anchored: each page starts at the last row of the previous one and checks it, reads one page further back when the list shifted, and restarts (at most eight times a pass) when nothing it read is still there. No row is skipped by a shift. members.pull reads one audience in last_changed order. The first pass walks every member; a finished pass carries the provider Date of its first page, and the next reads since_last_changed five minutes before it. Status stays explicit: unsubscribed with unsubscribeReason, cleaned (bounced), archived (a member DELETE). A permanently deleted member answers 404 like one that never existed and stays published. Whether a listing without a status filter includes archived members is undocumented. With updates: "webhooks", a signed audience webhook (X-Mailchimp-Signature: t=..,v1=.., HMAC-SHA256 over <t>.<body>, five minutes’ tolerance) requests a read; deliveries are form-encoded and name nothing. lists.pull and campaigns.pull walk everything each pass in creation order, which never changes; campaigns offer no last-changed filter. Deleted ones stay published. Not built: batch operations (status in a 200 body, results a gzipped tar on Google Cloud Storage outside the base URL). Nothing here has run against Mailchimp.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.