Constant Contact wants to help you succeed! We’re celebrating our professional service programs on the Constant Contact Community this month and you have a chance to try one of the services for free! Learn more.
Posting the following (faulty) XML
<title type="text" />
<ContactList id="http://api.constantcontact.com/ws/customers/test/lists/1" />
results in this error message
Error 400: The request contains errors in the common Atom sections, which lie outside <entry> or <Content>, such as <feed>, <id>, <author> or <updated>.
However, the error actually lies inside the <Content> element (which is really the <content> element), not outside as the error message will have us belive.
Could you please correct this error message so I don't waste more time looking for errors where there aren't any the next time?
substancelab.com - crafting quality web applications
I apologize for the inaccurate error messaging that you are receiving. I have forwarded this information on to the product manager to see if we can have this error messaging adjusted to be more accurate. Thank you for bringing this to our attention. If you have any other questions or concerns please feel free to post them on this forum.
I'm trying to do a similar post (for the first time using the CC API), and am getting the same error message - but I don't know how to diagnose exactly which part of my request is wrong. Any help on how to do that?
Here is my request body:
<entry xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2005/Atom">
<title type="text" />
Well, I figured out the problem in this particular case (duh):
Date formatting booboo.
That said, I still have the same general question about diagnosing such problems in general - is there no way you (CC) can include more specific into in the error message? Or, in the absense of that, is there any suggestions on other more reliable diagnosis techniques than "look and guess"?
I know what you mean--that error message isn't terribly helpful. I have actually brought that up to our quality engineering team to see if we can generate more helpful error messages.
Thanks for your feedback.
API Support Specialist