About igvinc

Hello Adrianne, In addition to Melanie's suggestions, you can also incorporate some educational content in the form of video.  You can use some of the staff to record them. ~Karen Leonard, panelist ... View more

We 1000% agree with you and have the same problem. We are working on a video to clearly document the problem and the way we are approaching it, perhaps it is Developer error on our end, but I wanted to confirm and say to you "yes... this is a problem... we see it too" ... View more

Sorry to say, yes, the refresh_token does indeed expire.   Maybe you can make a simple HTML/PHP form with a video showing us what you are doing? For example:  Document how to add 1 user to a specific list with 2 custom fields from a simple landing page with a custom form with a hardcoded API Key, Secret and Token - that does not expire   ... View more

Correct... sadly... so far we have the same problem: impossible to "add 1 user to a specific list with some custom fields from a simple PHP landing page with a custom form"   Ergo: Not solved ... View more

Same problem here. In V2 of the API We have a simple HTML/PHP signup form on a basic landing page We have an API key, a Secret, and a Token Users fills out the form, agrees to terms, gets a Double opt in Result: using the LIST_ID, and 2 custom fields the user is added to a specific list. done. (works great only in V2)   that brings us to v3...  :(. . . I think you are right, so far it has proven Impossible to accomplish the simple task of "adding 1 user to a specific list with some custom fields" No way to generate an access token that stays good long enough to leave the landing page up No way to add 1 user to a specific list Documentation does not make sense Constantly have to refresh the token No clear examples Examples given do not work Other problems we ran into: https://v3.developer.constantcontact.com/api_guide/contacts_create.html Create contacts has no explanation on how to add that 1 user to a specific list 'authorization' => 'Bearer {access_token}' Disambiguation needed Assume access_token = 12345 Does not work: '{12345}' Does not work: 'Bearer {12345}' Does not work: 'Bearer 12345' Does not work: '12345' access_token and refresh_token constantly expire Impossible to hardcode API_key, Secret, Token into a variable in PHP to allow landing pages to work Our Conclusion: V3 does not work for adding 1 contact to a list after they fill out a form.   Ergo: Our solution was and still is to use v2 (or switch to another platform that has a working API, which seems rude/inappropriate to talk about any further in this forum)   Sorry... but you are not alone! ... View more

I believe you are correct and I can confirm that I too have spent countless hours on this same issue. summary of problem: The refresh token expires. making it impossible to hard code anything into an application that will allow us to collect emails from a simple custom-built form using PHP. We have a simple newsletter on our website that uses version 2 of the API. every attempt I have made to use version 3 has failed... I took another stab at it today and I ended up in the same loop that you have ended up in. The refresh token continually expires every time I try to use it. ERGO: it is a never-ending paradox that is unsolvable. My conclusion was that I'll just stick with version 2. (or suggest clients use another newsletter platform) I've thought about making a video showing the problem... I think a good way to approach this is simply asking this question: is it possible for us to build a simple PHP form that has hard-coded our API key, API secret and 1 unchanging refresh token that will always be reliable forever collecting an email on a simple pop-up AJAX newsletter subscribe form? My conclusion was: no this is impossible. (I would very much like to be wrong about that.) ... View more

I want to double check here...   Is the following statement true or false: Every time we have a custom form on our website get filled out with a box checked "sign up for mailing list" we ALSO have to obtain a new access token and a new refresh token, store those tokens in a database, use them for the next request, over and over, forcing us to save data on our server (in a DB for example) with a new access token and a new refresh token for every user that fills out our contact form.   Or, is this statement true: Once we generate our first access token we can just use it, saving only that into a PHP var, manually, and then use it to get a new "refresh" token ... View more