Hello Courtney_E, thank you for reaching out! Based on the response that you are getting, which appears to be the html for Constant Contact’s login page, I suspect you may be trying to execute the OAuth2 authorization behind the scenes. The Authorization Request screen can only be accessed/authorized via a browser window or a pop up browser dialog, but you should only need to authorize/connect each account once via this method. I am interacting with the integration app via browser, and trying to use the browser to let the user log in (shown in the picture below). The problem I'm running into I'm just being given a Constant Contact error in the UI, instead of a login form. My app is running on http://localhost:8080/oauth When the user navigates to this page it makes a request to the Constant Contact Auth server, which responds with HTML I then redirect the user to this response HTML If I'm understanding correctly this is the initial auth flow outlined in the documentation. So I am curious what I may be missing that is causing this error to be displayed when the response is a 200 status. Again, I greatly appreciate your thoughts and help
... View more
Hello Constant Contact's API Support! I'm currently trying to use OAuth2 Authorization Code Flow to retrieve an authorization code for my integration. After making a request to the OAuth server, I am being returned a 200 status with some html in the response body, which I am rendering. Unfortunately the view where the user should be prompted to sign in to authenticate their user account is printing the message "There was an unexpected internal error. Please try again." Does anyone have any insight how I can resolve this? I've attached the source for my client app, and if I can provide any more context I would be happy to. I just want to get my authorization code! Thank you for any thoughts or help!
... View more