Account under maintenance returning unexpected exception codes.

[Isaac Grant]

Our MailChimp account has been under maintenance for a few hours this
morning, and the api is returning unexpected exception codes.

We use the 1.3 api, and wrap nicer exception handling around the MCAPI
mini v1.3.1 wrapper. We've been working off the list of exception
codes in the API documentation here:
http://apidocs.mailchimp.com/api/1.3/exceptions.field.php

Account Maintenance is listed as 105: User_UnderMaintenance, but our
calls are all returning the error code 120, which the documentation
says is User_InvalidAction, but the error message string returned by
the API is "Your account is currently under maintenance. Please check
back later."

Can you please explain what the difference between the exception codes
are, and whether the 105 code is behaving as expected from MailChimps
perspective?

Thanks,
Isaac

[Eric Muntz]

It seems you are hitting the API without prefixing the datacenter in
your calls. We made a DNS change for api.mailchimp.com that's yet to
fully propagate on the interwebs and the old location is returning
under maintenance for all users. You really should prefix your calls
with the datacenter specified in your API key. For example, if the
API key ends in "-us1", call the API at http://us1.api.mailchimp.com

This is noted here: http://apidocs.mailchimp.com/api/1.3/

That said, the error codes being returned in this specific case are a
bit wrong and we'll take a look at that.

-Eric

[Isaac Grant]

I'd appreciate a follow up when the error codes have been looked into
further so we can remove our temporary code to work around it.

For the record we are hitting the API on the prefixed version of the
url, using the MCAPImini 1.3.1 wrapper, and there appears to be
something wrong with our account. We've been in contact with support,
but I figure it can't hurt to cross-post here and follow up on your
response.

You can see a screenshot of a sample ping call to the api here, and
please note we are using SSL.
http://cl.ly/2i342r1O123H2U1h3X2l

On Jan 23, 2:04 pm, Eric Muntz <emu...@rsglab.com> wrote:
> It seems you are hitting the API without prefixing the datacenter in
> your calls.  We made a DNS change for api.mailchimp.com that's yet to
> fully propagate on the interwebs and the old location is returning
> under maintenance for all users.  You really should prefix your calls
> with the datacenter specified in your API key.  For example, if the

> API key ends in "-us1", call the API athttp://us1.api.mailchimp.com

[Eric Muntz]

Isaac, pretty sure your account is fixed now. I will ping back here
when we've looked into the error codes for this particular situation.

-Eric

On Jan 23, 1:52 pm, Isaac Grant <is...@silverorange.com> wrote:
> I'd appreciate a follow up when the error codes have been looked into
> further so we can remove our temporary code to work around it.
>
> For the record we are hitting the API on the prefixed version of the
> url, using the MCAPImini 1.3.1 wrapper, and there appears to be
> something wrong with our account. We've been in contact with support,
> but I figure it can't hurt to cross-post here and follow up on your
> response.
>
> You can see a screenshot of a sample ping call to the api here, and

> please note we are using SSL.http://cl.ly/2i342r1O123H2U1h3X2l

[Isaac Grant]

Yep, support let me know when it was fixed. Thanks for the follow up.

[Isaac]

Just wanted to check about whether the API has been updated to return the documented error code - we'd like to get rid of the hack in our wrapper that checks for the User_InvalidAction exception code.

Thanks,

Isaac

[jesse]

Yes, though I wouldn't suggest you just start ignoring that perfectly valid error code.


jesse