You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are obtaining account data using the Mailchimp Client, via the npm library.
When requesting data for the US18 data center, the request failed with a 400 status code for unknown reasons.
We're getting the following error: "Your client has issued a malformed or illegal request."
When we requested data for other data centers, the data was retrieved correctly.
Some of the reports we attempted to retrieve were: automations, lists, and campaigns.
We used a valid token, it worked when we tried to get data directly from the MailChimp API for us18 data center. mailchimp-error.txt
We received the following response: mailchimp-error.txt
Is there a reason why we can't get data when we use the MailChimp Client for us18 data center?
Any assistance is appreciated.
The text was updated successfully, but these errors were encountered:
SnirYadid
changed the title
reports for us18 dc no works when using client
bug: reports for us18 dc do not work when using Mailchimp Client
Jul 13, 2023
We are obtaining account data using the Mailchimp Client, via the npm library.
When requesting data for the US18 data center, the request failed with a 400 status code for unknown reasons.
We're getting the following error: "Your client has issued a malformed or illegal request."
When we requested data for other data centers, the data was retrieved correctly.
We're using the 3.0 version.
Base URL: https://us18.api.mailchimp.com/3.0
Some of the reports we attempted to retrieve were: automations, lists, and campaigns.
We used a valid token, it worked when we tried to get data directly from the MailChimp API for us18 data center.
mailchimp-error.txt
We received the following response:
mailchimp-error.txt
Is there a reason why we can't get data when we use the MailChimp Client for us18 data center?
Any assistance is appreciated.
The text was updated successfully, but these errors were encountered: