Hey David, Thanks for the reply. My apologies for my frustration but the last two weeks have found me dealing with multiple failures and issues at CC. I have other priorities but I can give you some details. I am using the older v1 for this client as they have been using it for some time, for simplicity, and legacy issues. Soon, I will either reintegrate with v2 or with another ESP. I've been waiting patiently for v3 but it seems to be taking quite some time and I'm concerned that it apparently does not include features like tag management, a critical feature for filtering and managing contacts in the UI and when sending campaigns. Do you have an ETA for API v3? I called support multiple times yesterday about this and other issues when I realized not contacts were stored by CC since Oct. 5th. Specifically, I was receiving a 200 response when testing updating a contact with the API. I've made changes now to correct the issues and I'm not able to repeat it. The basic endpoint being used is: https://api.constantcontact.com/ws/customers/... The custom fields are named CustomField1,4, and 5. This was seen during testing yesterday afternoon at multiple times. Regarding the 503 errors, I can't be sure about the time as I did not note it, but they were returned between 2:00-4:00 PM PDT yesterday, Oct. 12th, while I was testing and troubleshooting options to fix the error where contacts were not being added to CC since the 5th. I was performing the standard calls to POST a new contact, GET an existing contact, and PUT to update a contact. I'd note that I am also struggling to perform the client required integrations and management due to the additional shortcomings/issues outlined below. If these are fixed in v2 or v3 please let me know. Unable to GET a list of custom fields via the API Unable CRUD custom fields with actual names via the API Unable to manage tags via the API Unable to use dynamic links in emails to track anything outside CC in v3 of the editor When bulk editing lists or contacts, unable to see current tags or lists in UI When performing advanced searches in the UI, the results returned do not seem accurate according to the filters applied. Thanks!
... View more
There is a known issue causing API requests to fail without producing an error. If the API request includes custom fields it will return a 2xx response code but your contact will not be added to your CC account. This has been occurring since Oct. 5th at least. This was noted by a CC Mod in the thread below: https://community.constantcontact.com/t5/Developer-Support-ask-questions/Error-400-Received-Bad-HttpResponse-409-Conflict-ActiveRecord/td-p/305596 I am also getting this response intermittently when using the API: Service Unavailable: Back-end server is at capacity 503
... View more
My client is suffering from the same issue. All API requests sent to CC from our website since Oct. 5th have not been added to our CC account. We have lost multiple new contacts due to this issue as the contacts are primarily stored in CC. The only option to many of them into CC now is to manually create a list from individual emails sent to the contact. Guess I'll have to store the contacts elsewhere as CC is apparently not reliable.
I'm also intermittently getting this response from the CC API: Service Unavailable: Back-end server is at capacity 503. WTH?
Additionally, the API returns a success message so an API integration will think it's working even though it's not. THE API DOES NOT RETURN AN ERROR CODE! Why was there no notification about this issue sent to developers or a sticky post noting this issue in this forum? I had to drill into threads here to find this post. FFS, I just spent 5 hours troubleshooting this issue, finally determining it was an issue with the custom fields. I can confirm that removing the custom fields seems to fix the issue.
I want a credit for at least the last month of service! Not happy!
... View more
This is critical functionality for various reasons including managing subscribed lists based on actions taken by a contact and to track affiliate/partner conversions via links. This severely limits transactional email options. The fact that this is not available currently and is apparently not a priority is baffling. It seems CC is focused on simple use cases that do not include API integrations and serious marketing. I'm frustrated that I have spent time developing to an API where maintenance and functionality is not a priority. Other developers beware! These are additional issues: Unable to GET a list of custom fields via the API Unable CRUD custom fields with names via the API Just recently the options to update custom fields via the API have stopped working Unable to manage tags via the API Unable to use dynamic links When editing lists or contacts, unable to see current tags or lists in UI Receiving this response intermittently when using the API: Service Unavailable: Back-end server is at capacity 503
... View more