About WCCGoldenApple

Are there any SDKs for PHP 5.6 and below that anyone knows about? We do not have the ability to upgrade our PHP at the moment. ... View more

Hey Constant Contact support,   Looks like you lost a customer because you are not recommending a fully supported PHP API package that completely implements your API and is updated nightly.   If you ask me, that is really bad form.  I have done your job for over 40 years, and I can say losing a client due to bad support is simply not a good business strategy. You have a gift from me.  Use it!  Don't give the cop out answer of you are going to implement something eventually, when you know you don't want to bother, or you are not smart enough to do it yourself.  My library is completely open source.  You are more than welcome to take over the project, or even use my code and logic to implement other language versions.  C++ is a big market. Use my techniques and implement your own C++ wrapper.  Python, Ruby and other back end languages can be easily added with minimal effort.  I have shown you the way.   Happy to help you succeed, but I can only lead a horse to water.   Good luck pissing off clients!  Been there done that.  Losing strategy.   Be a hero and tell management that you can provide full support for most back end languages with very little effort.  You will be a super star.  Trust me.  Just do it! ... View more

Hello HeidiS146,   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 looks like we're already working with you directly via email, but I wanted to close the loop here as well. If you haven't received our reply, please let us know via email at webservices@constantcontact.com, and reference case number 29664639. ... View more

Hello JuneL4,   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 looks like you received this communication because a V3 API key was previously generated within your account, but based on the code sample that you provided, it looks like you are currently using our legacy V2 API, which will not be affected by the new authorization management service being used for V3.   However, while no date is currently set, there will be a point in the future where our legacy V2 API will begin deprecation, as the deprecation process for our retired V1 API is nearly complete. Due to this, while we will continue to deploy critical bug fixes at this time, we will not be doing any more development for V2 or its endpoints, and strongly recommend upgrading to the V3 API to ensure you're ahead of the curve.   In your second example, it looks like you are using the V3 cross reference endpoints listed within the Data Migration Overview documentation to get a V3 List ID. You can also utilize our API Reference Page to find these values, as well as body schemas, and also test the functionality of our available V3 endpoints to see how they will work once programmed within your application: https://v3.developer.constantcontact.com/api_reference/index.html   As you go through the upgrade process, please feel free to email our team directly/securely at webservices@constantcontact.com with any questions you might have regarding V3’s authentication process, endpoints and functionality. ... View more

Hello RobertD8278 ,   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.   The request for V3 application code samples is currently under review. However, we're currently still adding endpoints and capabilities to the V3 API, and do not plan to publish official SDKs or sample apps until that process is complete. Your feedback and experience with this request is essential to improving our product, so thank you for reaching out to us regarding this matter. ... View more

Hello WCCGoldenApple,   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.   We greatly appreciate you bringing this to our attention. It looks like we have already reported this issue to our development team in response to your previous post: https://community.constantcontact.com/t5/Developer-Support-ask-questions/One-or-more-scopes-are-not-configured-for-the-authorization/m-p/383963/highlight/true#M12918   Please have a look and let us know if you have any other questions! ... View more

Hello @WCCGoldenApple , @QgivP & @user915548,    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.   We greatly appreciate you bringing this to our attention. We have been able to replicate the invalid scope responses you have received when encoding the scopes portion of the authorization request URL. I’m going to bring this to our development team for further investigation and update our documentation accordingly. In the meantime, we have found through testing that excluding the scopes portion of the URL from being encoded so the “+” characters generate as “+” and not “%2B” will allow the authorization request to be successful.    Please let us know if you have any other questions!   Regards, ... View more

CollinS62887, I would recommend using my PHP 8.0 API for CC V3.  Later this week I will be shipping a new client that is compatible with the new OAuth2 requirements, but the interface for you will not change.  Your code looks like it should be very easy to port.   You can find it here: https://packagist.org/packages/phpfui/constantcontact ... View more

Yes, that was it.  Someone else set it up and sent me a screen shot, which looked good.  But apparently something was off. ... View more

David, as this is an older post, you probably already solved your problem, but I decided to write a PHP V3 API wrapper.   Check it out at https://packagist.org/packages/phpfui/constantcontact  You can also view the complete source code and documentation at http://phpfui.com/?n=PHPFUI%5CConstantContact.   It is a full implementation of the Constant Contact V3 API and updated nightly with any changes that are made to the YAML file.   If you need to do additional things, or need the latest API, it might make sense to take a look, rather than write it yourself. It also has a nice next() function to get paginated results.  Super easy to use.   Hope this helps. ... View more

Hello Kevin,   My name is Caleb and I am a member of Constant Contact's API Developer Support Team.   When using the authorization URL a user will always be prompted to login to the account they would like to grant the application access to unless that user is currently logged into a Constant Contact account that has previously authorized the application. Typically this action only occurs when first using a new integration as once they have provided permission for the application to make changes to the account the application will have an access token to make calls with.   In your circumstance, you are attempting to re-authorize the application on your new system which did not have a Constant Contact account logged in, this prompted the request to login to the account and authorize the application again. Once the user has authorized the application on their machine you should be able to prevent them from needing to re-login by keeping the tokens refreshed.   Additionally, if you are connecting to Constant Contact as the same user on both systems without sharing your token information you will find that the two instances of the application will invalidate the other's tokens. To prevent this issue there will be a couple of different solutions. The optimal solution to this issue would be to share the token information over a shared server which would allow the application to always stay authenticated and would prevent the need for the users to login when signing in on a new machine. If this option is not available you will then want to either have each instance of the application use a new API key or you will want to sign into the Constant Contact account using a different users login information for each instance as the access token is unique to the user which signed in.   Moving forward, once the application has been authorized you will then want to have your application keep itself authorized with the account by utilizing the the refresh token found in step 5 of the OAuth 2.0 Server Flow. Below I have linked to the documentation which covers this as well as a link to how to keep these tokens active.   OAuth 2.0 Server Flow: https://developer.constantcontact.com/api_guide/server_flow.html   Extending the Life of Tokens: https://developer.constantcontact.com/api_guide/faqs_manage_applications.html ... View more

Glad to help and I hope it helps someone.  Certainly easier to use a library than figure it all out from scratch.   I did notice in the YAML file you have a few typos!  Change <a/> to </a> globally in the YAML file and you should be good.  A developer can do this in about 1 minute.  You can see the issue here: Account Emails get documentation error The problem is in the documentation for the get method.  The link is not terminated correctly, so continues on.   And feel free to use this library as a basis for yours, or just send people to mine.  It will save you a lot of PHP support questions! ... View more