Thanks Xiaoming. It works. I didn't realise setting up the refresh token is
an one time process.
Regards
Niyas
On Tuesday, October 22, 2019 at 4:29:39 PM UTC+1, adsapiforumadvisor wrote:
>
> Hi Niyas,
>
> The user consent is just one time activity that occurs when you set up the
> credentials f
Hi Niyas,
The user consent is just one time activity that occurs when you set up the
credentials for OAuth2 for the first time. OAuth2 access tokens expire after a
limited time. For this reason, the client libraries use the OAuth2 refresh
token to automatically regenerate the OAuth2 access toke
Hi Xiaoming,
Thanks for your response. I did go through the link you sent across. I can
see user consent is required to obtain the authorisation code. This code is
then used to obtain refresh token. Can you please confirm if obtaining the
authorisation code is a one time activity and the author
Hi Niyas,
Thanks for reaching out. You actually don’t need to worry about asking for user
consent and pulling data from the Adwords API. Your system would be able to
continually get authentication by using the refresh token mechanism and the
data would be pulled whenever your system makes the r
Hi,
In my project, we are required to extract Adwords data using Adwords API
using Azure Data Factory (Orchestration/ETL tool in Azure). This needs to
run without asking for user consent as the jobs are running in the
background.
Can you please help with the steps involved in authorisation wi