Title: API Request Error
Last modified: June 7, 2022

---

# API Request Error

 *  Resolved [2startltd](https://wordpress.org/support/users/2startltd/)
 * (@2startltd)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/api-request-error-14/)
 * We have seen an issue since 06/06/2022 where products are not syncing from the
   Mailchimp for WooCommerce plugin to Mailchimp, then I dug in to find the below
   error:
 * The WooCommerce Mailchimp plugin has thrown the following error and has brought
   our entire site to a grinding halt with the vast number of Ajax requests failing.
 * Details:
    `Mailchimp for WooCommerce Plugin Version: Version 2.6.2` `WooCommerce
   Version: Version 6.5.1` `WordPress Version: Version: 6.0`
 * Error thrown:
    `Mailchimp says: API Request Error - on 1970 in /wp-content/plugins/
   mailchimp-for-woocommerce/includes/api/class-mailchimp-api.php`
 * We have tried uninstalling and re-installing fully to no avail and the same error
   is thrown again.

Viewing 7 replies - 1 through 7 (of 7 total)

 *  Plugin Support [khungate](https://wordpress.org/support/users/khungate/)
 * (@khungate)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/api-request-error-14/#post-15716654)
 * [@2startltd](https://wordpress.org/support/users/2startltd/), this is most likely
   related to Mailchimp’s Akamai server blocking your server. Give this thread a
   look with troubleshooting options: [https://wordpress.org/support/topic/mailchimp-says-api-request-error-0/](https://wordpress.org/support/topic/mailchimp-says-api-request-error-0/).
 * Let us know if you get stumped or are able to figure things out.
 *  Thread Starter [2startltd](https://wordpress.org/support/users/2startltd/)
 * (@2startltd)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/api-request-error-14/#post-15716695)
 * Thanks [@khungate](https://wordpress.org/support/users/khungate/)
 * I had already skimmed this article earlier but will walk through the points more
   specifically related to our host’s IP being blocked tomorrow with them to see
   if this provides any further insight.
 * It’s been fine for over 6 months which makes this even more frustrating and no
   real notification that it was having any issue, just consuming our server’s resources
   which made me dig and find the error.
 *  Plugin Author [ryanhungate](https://wordpress.org/support/users/ryanhungate/)
 * (@ryanhungate)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/api-request-error-14/#post-15761313)
 * [@2startltd](https://wordpress.org/support/users/2startltd/) not sure if you’ve
   resolved this issue just yet with your server admins but if you haven’t – please
   try to use the docs [here](https://github.com/mailchimp/mc-woocommerce/wiki/Troubleshooting-CURL-Errors)
   and also a setting [here](https://github.com/mailchimp/mc-woocommerce/wiki/Configuration-for-outbound-IP-address)
   for setting the proper “outgoing IP address” being used for PHP CURL.
 *  Thread Starter [2startltd](https://wordpress.org/support/users/2startltd/)
 * (@2startltd)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/api-request-error-14/#post-15777264)
 * Hi [@ryanhungate](https://wordpress.org/support/users/ryanhungate/)
 * No, we have not resolved this yet, the staging server is allocated for another
   larger task at the moment.
 * I am still seeing the following error message whenever we activate the plugin:
 * `Mailchimp says: API Request Error - 503 :: on 1970 in /public/wp-content/plugins/
   mailchimp-for-woocommerce/includes/api/class-mailchimp-api.php`
    -  This reply was modified 3 years, 11 months ago by [2startltd](https://wordpress.org/support/users/2startltd/).
 *  Plugin Author [ryanhungate](https://wordpress.org/support/users/ryanhungate/)
 * (@ryanhungate)
 * [3 years, 10 months ago](https://wordpress.org/support/topic/api-request-error-14/#post-15807364)
 * [@2startltd](https://wordpress.org/support/users/2startltd/) sorry for missing
   this before but if you could please verify that you’ve tried both of the recommendations
   we said previously that would be helpful. It could be as simple as that just 
   adding the IP configuration option.
 *  Thread Starter [2startltd](https://wordpress.org/support/users/2startltd/)
 * (@2startltd)
 * [3 years, 10 months ago](https://wordpress.org/support/topic/api-request-error-14/#post-15808334)
 * Hi [@ryanhungate](https://wordpress.org/support/users/ryanhungate/)
 * This was causing so much of an issue with our server we have disabled the plugin
   fully and until our new site goes live, I will not be able to look at this further.
 * Thanks for checking in.
 *  Plugin Author [ryanhungate](https://wordpress.org/support/users/ryanhungate/)
 * (@ryanhungate)
 * [3 years, 10 months ago](https://wordpress.org/support/topic/api-request-error-14/#post-15809308)
 * [@2startltd](https://wordpress.org/support/users/2startltd/) no problem. We’re
   here to help when you get further along with the live site. Will close for now
   but feel free to ping us here when it’s time.

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘API Request Error’ is closed to new replies.

 * ![](https://ps.w.org/mailchimp-for-woocommerce/assets/icon-256x256.png?rev=1509501)
 * [Mailchimp for WooCommerce](https://wordpress.org/plugins/mailchimp-for-woocommerce/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/mailchimp-for-woocommerce/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/mailchimp-for-woocommerce/)
 * [Active Topics](https://wordpress.org/support/plugin/mailchimp-for-woocommerce/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/mailchimp-for-woocommerce/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/mailchimp-for-woocommerce/reviews/)

## Tags

 * [API error](https://wordpress.org/support/topic-tag/api-error/)

 * 7 replies
 * 3 participants
 * Last reply from: [ryanhungate](https://wordpress.org/support/users/ryanhungate/)
 * Last activity: [3 years, 10 months ago](https://wordpress.org/support/topic/api-request-error-14/#post-15809308)
 * Status: resolved