Mailchimp | Operate As Docs

Connect your client's Mailchimp with a key they paste, and call its API through Operate As.

Website: mailchimp.com
Connects by: Pasting a API key
Category: Marketing
Services: 1
Tools: 303

Service	Key	Base URL
Mailchimp	`mailchimp`	`https://{dc}.api.mailchimp.com/3.0`

Your client also types their data center (The end of your API key, after the dash, such as us6).

Connecting

Your client makes a API key in their Mailchimp settings and pastes it on their link. Operate As tries it with Mailchimp before saving it, and stores it encrypted. See Services connected with an API key.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "mailchimp"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "mailchimp"    ]  }]

Permissions

What the client reads	Permission it asks for
Use the Mailchimp key you paste, with only the access you gave that key	Chosen on the provider's screen

Tools

Install Mailchimp's typed package for your language:

pip install operate-as-mailchimp

pip install operate-as-mailchimp

Run mailchimp.archive_automations

curl -X POST https://api.operate.as/v1/actions/mailchimp.archive_automations \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "6f1c2a7e-...",
    "input": {
      "workflow_id": "<workflow_id>"
    }
  }'

curl -X POST https://api.operate.as/v1/actions/mailchimp.archive_automations \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {      "workflow_id": "<workflow_id>"    }  }'

Shows the required inputs. Every input, with its JSON Schema: GET /v1/actions/mailchimp.archive_automations

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://{dc}.api.mailchimp.com/3.0, with the parts in braces filled in from your client's account. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../mailchimp/ping" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../mailchimp/ping" \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

A key works until your client deletes it in Mailchimp. They can paste a new one on the same link at any time, and your workflows carry on without changes.

See Keeping access alive and Removing access.

Calls answer, once the key is deleted

{
  "status": 401,
  "data": {
    "…": "the service's own error"
  },
  "encoding": "json"
}

{  "status": 401,  "data": {    "…": "the service's own error"  },  "encoding": "json"}