Device Flow without any user interaction to obtain Access Token

[BrianB7795]

I working with the following documentation 

https://v3.developer.constantcontact.com/api_guide/device_flow.html 

And I am able to obtain an authorization response just fine however, Step 2 is where I am getting stuck.

Step 2: Provide Authentication and Authorization Information to the User

Your application provides the the information the user needs to authenticate their user account and to authorize your application from a device using a web browser, such as a cell phone. How you choose to provide the information is up to you.

You can choose to provide the user with:

• The URI to use and the code to enter.
• The QR code to scan to open the URL and the code to enter, or a shortened URL to use that includes the embedded user code.
• If running natively on a browser-based device, returns the direct verification URI with embedded code.

Once I get the response I can click on the link that provides the code and once I have that I obtain a token however, this is not truly device flow since it is still requiring user interaction. 

Is there away to perform step to pragmatically without actual user interaction? I have tried polling the token but it keeps returning authorization_pending until it eventually times out. 

I am stuck and would like to know if this is even possible. I have done this with Azure but, well, that's Azure. 

Thanks!

[John__B]

Hello BrianB7795,

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.

Each of our available authorization flows requires the use of a browser window for a Constant Contact user to authorize an application/integration on their account, however, you should only need to do this once as after authorization has been granted, your application/integration can utilize Refresh Tokens to maintain account access.

Please let us know if you have any other questions!

Regards,