Can't create an authorization code

@andrew_videoask Ohh really! Thank you so much! 

I was confused by documentation 

@Yuriy The previous paragraph mentions that the request should be made through a browser, though I definitely understand your confusion!

Thanks for your feedback. I hope we can update the authentication documentation soon to make it more user-friendly 🙂

@andrew_videoask Yeah, thanks!

@andrew_videoask I think the docs could be worded better, especially around refresh_token: I ended up having to use Auth0 docs directly: https://auth0.com/docs/secure/tokens/refresh-tokens/get-refresh-tokens

For anybody coming across this, here is the flow if you need a refresh token that can mint new access tokens:

1. You authorise your app in the browser
   https://auth.videoask.com/authorize?response_type=code&audience=https://api.videoask.com/&client_id=${your_client_id}&scope=openid%20profile%20email%20offline_access&redirect_uri=${your_redirect_url}
   
   You should receive a code parameter in the querystring of the callback
    
2. You then need to make a POST to the token endpoint once

   curl --request POST \
     --url 'https://auth.videoask.com/oauth/token' \
     --header 'content-type: application/x-www-form-urlencoded' \
     --data grant_type=authorization_code \
     --data 'client_id={yourClientId}' \
     --data 'client_secret={yourClientSecret}' \
     --data 'code={yourCodeFromPreviousStep}' \
     --data 'redirect_uri={https://yourApp/callback}'

   In this response, you should see the refresh_token which can be used for asynchronous, long-term access

My reading of the docs is that it sounds like you’ll get the refresh_token in the response to the offline_access scoped authorize call – you won’t.

Hey @Fork thank you so much for sharing this, I’m sure people trying to navigate the API docs will appreciate your help and I will be passing this onto the team to review as we continue to update the API and documentation 🙏