I am a developer for poptin.com and I am working on an integration with Constant Contact. I am using OAuth to authenticate with your platform. But there seems to be an issue, when the user authorizes a second time, the tokens that were issued on the first time become invalid. This doesn't happen with OAuth on other platforms. Is this a security thing? In Poptin, the client can choose to connect the Constant Contact integration in a few places, but as soon as they will try to authenticate and connect in multiple places, old integrations will stop working. How to work around this? Is there a way there to make the authentication work with multiple tokens?
Hi, For our API team, please reach to firstname.lastname@example.org. You should receive a response within one business day depending on time of day and volumes. Thank you!
it would help other developers if an answer to the OP's question was posted in this same thread.
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.
When it comes to Access Tokens they do expire/overwrite after a certain amount of time or when a user generates a new Access Token depending on which API version they're using. This was implemented as a security measure, if you need multiple Access Tokens on an account for our V2 API the only workaround at this time would be to have multiple users on the account that way they can all have a separate Access Tokens. Our V3 API on the other hand does not offer static Access Tokens as they expire every 2 hours. Just in case, below are links to documentation on Access Tokens for both our V3 and V2 APIs.
V3 API (Expires)
V2 API (Overwrites)
Please reply directly to this post if you have any other questions!
View API documentation, code samples, get your API key.Visit Page
Join our list to be notified of new features and updates to our V3 API.Sign Up