MailChimp API

  • Are you guys planning on updating this plugin to use the MailChimp API instead of username/password/sopresto ?

    I’m working on a client’s site, and for development, I have the site in a password protected directory on the web server. Because of this, I can not use this plugin… the connector won’t connect because it’s trying to post back and can’t authenticate (401 error).

    Using the API would be much simpler, no?

    I’d prefer to use your stuff for this if possible rather than using a 3rd party plugin.

    https://www.ads-software.com/plugins/mailchimp/

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

  • Hey Thor.worx,

    The plugin actually uses the API itself, with only authentication being set up to use OAuth via the username and password approach rather than requesting an API Key. The move to OAuth for authentication over a copied and pasted API key was a change made recently and one that is generally recommended for plugin creators moving forward. Otherwise the API is still used in the same manner, but the authentication is made more securely.

    That said, we do have a “Developer Mode” which may help in this case. It’s specifically for using the plugin within development environments inaccessible by/from external systems. We have a guide on that here:
    https://connect.mailchimp.com/how-to/90

    Beyond that, it may be necessary to look into a third party plugin, though we’re certainly happy to answer any other questions you have!

    -Gabe

    Thread Starter Thorworx

    (@thorworx-1)

    Hey Gabe,

    Another potential issue related to this:

    As a developer, I help my clients set up their Mailchimp accounts.
    I have access to several clients accounts within MY Mailchimp account.
    If a client already has a Mailchimp account, I ask them to add me as an admin so that I can help them with templates, forms, etc.

    With this plugin NOT using API keys, on my clients’ sites, I login with *my* account and choose the client’s account to grab the lists.

    So far so good…

    However, what happens if/when a client ever removes me as an Admin?
    Presumably, the plugin will no longer be able to connect to the client’s lists.

    For this reason, I think this makes a strong case for using API keys vs. OAuth. It seems to me that the plugin should be API key specific, not account specific.

    Hi Thor.worx,

    The plugin uses oauth2 for a number reasons including making it easy to login without looking for an api key. At this time, there aren’t any plans to move back to api keys. If your clients are going to potentially remove admin access, you might consider having them login through the WordPress admin area with the owner MailChimp account.

    Previous versions of the plugin that used api keys are still available to download.
    Checkout this page for previous versions of the plugin: https://www.ads-software.com/plugins/mailchimp/developers/ Any version earlier than 1.3 used api keys for account access. But I would warn you that those versions are no longer supported.

    Let us know if you have any other questions.

    -mc_d

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘MailChimp API’ is closed to new replies.