Hi Elijah,   Yes, I noticed a couple weeks ago that issue appeared to have been corrected.   Thank you for taking care of it,   Karl ... View more

Hi Elijah,   Is the "mailing system" used by the API the same "mailing system" that is used when I create a custom email via the constantcontact.com website?  If so, then why would my result from the website look like this:   I also did a little more digging and when I look at the message footer of a campaign that I created via the API I see this:   But, when I look at message footer of the email campaign that I created via the website directly, I see this:   This gives the appearance to me that the API may not be properly feeding the data to the system and perhaps that is why we are seeing the difference in the footer that is delivered to our customers.   Beyond that, if you are saying that the only way for me to display a 2-character code in the footer is to create a non-US value, then can you provide me with the proper values to setup that footer?   Thanks again for your help,   Karl ... View more

Unfortunately, that solution causes the following error when I attempt to create the new campaign:   json.field.message_footer.state.invalid:Instance value does not match any String value. Valid options are: AL, AK, AZ, AR, AA, AE, AP, CA, CO, CT, DE, DC, FL, GA, HI, ID, IL, IN, IA, KS, KY, LA, ME, MD, MA, MI, MN, MS, MO, MT, NE, NV, NH, NJ, NM, NY, NC, ND, OH, OK, OR, PA, RI, SC, SD, TN, TX, UT, VT, VA, WA, WV, WI, WY. json.field.required.us.address.fields.missing:state and postal_code need to be set if country is set to US.   So it looks like I would also need to change the Country, is that true?  And if so to what do I change it?   And then let's discuss whether what we are suggesting to do here makes logical sense... If the footer using the default address from the account, then the state is displayed using the 2 digit Postal Code.  So why would we stray away from that when we pass a postal code in a custom footer structure?   I would think a much better interface would allow me to pass in AL or ALABAMA, but not BAMA, and it would ignore character case in the validation giving the user the ability to display their footer address in all lowercase or all uppercase or any mix in between.    ... View more

When I do the //api.constantcontact.com/v2/account/info call,  I get my 2 digit home state abbreviation for "state_code" in the main structure and in the "organization_addresses" structure.  I only have 1 address in that structure.  There is not a "state" property in the structure at all.   When I look at the campaign via the //api.constantcontact.com/v2/emailmarketing/campaigns/<campaignId> call, I can see that the "message_footer" has a "state" property which is set to "CA" (in the test campaign I'm currently looking at), the "international_state" is an empty string.  There are no other "state" type properties in the structure (not even in my "email_content").  However... That is the result on the email.   Here's a screen print of the footer...       ... View more

Thanks, I saw and I have set my message footer up according to the documentation... setting the "state" propery to "MA" as shown in the documentation.   The problem is that when the email is delivered, it displays "MASSACHUSETTS" instead of "MA" and I really don't want my custom email yelling the state name.   Is there some indicator that tells it to use the abbreviation rather than the full name? ... View more

If you are using the .NET SDK, take a look at the HttpRequest method in the RestClient Class of the CTCTWrapper project (..\.net-sdk-master\TCTWrapper\Util\RestClient.cs).  Look to see if the method is throwing an exception when the response.StatusCode is not equal to HttpStatusCode.OK.   If you find that it is throwing an exception in this situation, then this is probably what is causing your issue.  Creating a List returns HttpStatusCode.Created response code rather than HttpStatusCode.OK.   ... View more