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

I had the same issue as you did. No good PHP V3 wrapper for the Constant Contact API.  So I wrote my own!  And it is available on Packagist.org. https://packagist.org/packages/phpfui/constantcontact Updated nightly due to automation.  All API endpoints are implemented, and fully supported.   Let me know if you have any problems / question by submitting an issue on github. ... View more

I had a similar problem.  Turns out you used to need to URL encode the + symbol that separated the scopes using %2B, but now you just need to use the actual + sign.  Someone else pointed this out to me.  Just passing it on.  CC support has been less than helpful here with an obvious error in their API that should have been fixed long ago.  API should take either %2B or +.   ... View more

JuneL4,   Looks like you are using PHP.  The new OAuth2 server requires a more complex handshake than the old one.  It is not a trivial fix.  I would recommend you use my V3 API library, but will require rewriting your code and PHP 8.0.  But the upside is you will be insulated from future changes.  More details here: https://packagist.org/packages/phpfui/constantcontact ... View more

I have not tagged a new release yet, as I want some testing done on it.  I did post an  update yesterday, so it should be good.  Install as normal with composer then change the version requirement to "dev-main" and do a "composer update" and you should be good to go.   Any issues, just open an issue (or PR if you want to contribute back, but not required) and I will try to get things fixed. ... 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

Bob, not sure what the ctctWrapper V1 is, but Constant Contact is no longer supporting client libraries for their APIs.  I don't blame them really, they are a lot of work to maintain.   I wrote a PHP wrapper for the V3 API.  You can find it here: https://packagist.org/packages/phpfui/constantcontact  Very easy to use, as it creates typed objects that you can send and receive with the API.  The current version does not support the new OAuth2 PKCE stuff, but I will have an update later this week that will, being tested now.   Hope this helps. ... View more

@QgivP ,    That was the problem.  I needed to change the correctly encoded URL with %2B to the normal plus (+) character!  I will see if I can submit a bug report.    Thanks! ... 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

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

I actually just this for PHP.  You can find it here PHPFUI\ConstantContact Basically had the same problem, but came up with a reasonable solution.  Check out the readme, but essentially you need to make your user authenticate the app, then you save off the tokens and do a periodic token refresh.  The token should then not expire.   Also the library is generated off the YAML file and updated nightly.  So any change to the YAML file produces a new version of the library, so it is always 100% up to date with the API schema.  There is a Generator class that writes out the appropriate PHP files.  Since PHP and C# are very similar (Java or C++ type languages), it should be very easy to port this library to C#.   Feel free to copy the design.  Enjoy!   ... View more