About Elijah_G

Hello Kmayer21,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   It's our understanding that this issue is caused due to Outlook not supporting "px" or setting these variables in the style attribute. The following workaround is suggested to bypass this display issue:  Change the code so that it does not use the 'px' for the size and also has the height and width set individually.   In case it is helpful, I have also linked the following article which contains a List of supported HTML tags for Custom Code emails within the current Custom Code editor, as the old editor was retired since this thread was originally created.   Errors in a custom code email https://knowledgebase.constantcontact.com/articles/KnowledgeBase/33242-Errors-in-a-Custom-Code-Email   If you have further questions regarding Custom Code emails, please feel free to reach out to Constant Contact's Support Team at 866-289-2101 and request to be connected with a Custom Code specialist. Your case number for reference is #31433001. ... View more

Learn the difference - https://scaramanga.agency/articles/2021/do-you-know-your-straight-from-your-curlies-using-the-right-quotation-marks-is-just-smarter ... View more

Thank you for reaching out to Constant Contact API Developer Support and for your patience. My team is here to assist outside software developers with questions about building into Constant Contact's API.   We're still in the process of rolling out new endpoints for Tags support in the V3 API.   It looks like a bulk activity endpoint to remove Tags has been published, but as of just yet, there is no bulk endpoint for adding Tags: https://developer.constantcontact.com/api_reference/index.html#!/Bulk_Activities/postTagRemoveContact   There are also Tag capabilities in the body schema for creating or updating an individual contact, but none for the sign_up_form endpoint currently: https://developer.constantcontact.com/api_guide/tags_overview.html   We look forward to making new endpoints available for Tags. You can keep up to date on the latest available V3 endpoints here: https://developer.constantcontact.com/api_guide/release_notes.html ... View more

Hi @VC1977,   This thread is several years old and refers to our v1 API which is deprecated. Are you using the v1 API and encountering this issue, or are you using our v2 or v3 API? If you are using our v1 API I would highly recommend to look in to updating to one of our other versions. ... View more

Hi Jimmy,   Thanks for your reply. I understand this could be for security reasons. I noticed in CTCT API we cannot revoke a refresh token and I guess that's why such auto invalidation is needed.   As to how often would this occur, from my experience it's very common to have subscription forms on websites nowadays, especially for marketing websites. And it's also very common, as you can imagine, that CTCT customers could run multiple websites and taking subscriptions from different websites and send them to different lists to segment contacts, it's how email marketing businesses work these days.    If there's no solution we need to make the customers aware of it (or our plugin will look buggy). And we then probably suggest users register their apps if that's the case. We'd really appreciate if it's something can be changed in the API, since we all know for non-techy people, registering their own apps will be a challenging work.   When you get the chance, can you let me know your team's decision on it? Thank you! ... View more

Yes and thank you!!!!! Will need to add the if statment to my loop, that is great thank you so much!!   ... View more

Hello,   Thank you for the feedback! In this case it's a bit complicated, as the document you linked is specific to our V1 API which does not have the same errors as our V2 API. This is a bit tricky to document for V2 as we opted to show the status codes on a per-endpoint basis rather than having a global table. In particular this code doesn't make a great deal of sense to document on every endpoint, as it only shows up when you've entered the URL incorrectly and are not calling a valid service that would contain a valid endpoint.   I'll chat with the team here and see if we can come up with a way to document this better!   Sincerely, ... View more

Hi Richard,   Thank you for your feedback on this and for sharing your experience with us. In this case, it is not likely that this will change, as the limitation that a redirect URI must always match is part of the OAuth 2.0 specification that we are implementing for authentication. Because this is a core part of the OAuth implementation, it is not likely that it will be changed. One aspect of that limitation is that this leaves using a central agent that can pass that redirect on to the correct user as the only option to implement this properly.   Best Regards, ... View more