Did the API changed yesterday? Suddenly seeing errors for US country with null state/province code

Participant

Did the API changed yesterday? Suddenly seeing errors for US country with null state/province code

We've suddenly started seeing errors for users trying to subscribe using the USA country code ('us') and a null value for the state code.  This only started yesterday - has the API changed; and are API calls now forced to provide the state code when country is set to USA?

 

I've checked the release log and can't see anything scheduled for yesterday, so I have no idea why this has suddenly stopped working (we've made no code changes in the last few months).

 

FYI, we're using the C#.NET wrapper, and this is throwing a CTCTException: 

 

"json.field.address.state.and.country.mismatch:#/addresses/0/state: The attribute value is not valid for the country code us. Must be a valid US State or Canadian Province.\r\n"

 

Any ideas?

 

Thanks in advance.

1 REPLY 1
Moderator

We have identified a bug that was inadvertently created when a fix for a separate issue was pushed to production on Wednesday of this week. Please see issue WS5664 in the open issues list on our developer portal here:

http://developer.constantcontact.com/docs/api-issues-and-status/open-issues.html

 

We are getting this bug into the queue for fixing, and the issue will be updated with a fix ETA when it becomes available.

Rich Marcucella
Sr. Technical Writer, Content Developer
Web Services Team
http://developer.constantcontact.com
Developer Portal

View API documentation, code samples, get your API key.

Visit Page