Deauthorize/disconnect app in development from account?

[CarlG47]

Hello,

I have created an App under "My Applications", authorized the app using the same account, and successfully used the API. I would now like to go through the app authorization step again from the start but I don't see how to deauthorize/remove this application from my account. If I attempt to authorize again I'm automatically redirected and don't see the authorization/approval screen.

I expect to see this App on the Tools > Apps & Integrations > Connected Integrations option, but don't see anything there.

How can I deauthorize or remove an app from my account? I'm not trying to delete the app itself, but just the authorization from the user side.

Thanks,

[John__B]

Hello CarlG47,

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 have a feature request open to accommodate the functionality of deauthorizing/disconnecting applications from Constant Contact accounts in the website UI, however, I’m unable to provide an ETA on when that will be available at this time. For the meantime, the best workaround I can recommend would be to invalidate the refresh_token to end the connection between the application and the account.

This can be done by sending a new refresh_token request using the same refresh_token value used the last time the token set was refreshed. Doing this one or two times with the same refresh_token value should result in an “invalid_grant” error response. The only way to generate a new access_token for the account at this point would be to re-authorize the application with the authorization request. Please note that this method will not work if the “Long Lived Refresh Tokens” option is selected under the “OAuth2” tab of your key’s settings. 

I would also note that even if the refresh_token has been invalidated, we currently will not display the prompt to accept the scopes that the account user has already authorized when making the new authorization request. The best workaround I can recommend for making the prompt appear again would be to either add new scopes to the authorization request or authorize the application on the account with a different account user.

Please have a look and let us know if you have any other questions!

Regards,