Hi Darwin,
We are not really creating a specific app, we are basically just using
POSTMAN and INFORMATICA CLOUD to automate getting data and loading into our
Snowflake database. Does that answer your question?
Minyen
On Wednesday, November 9, 2022 at 12:46:57 AM UTC-6 adsapi wrote:
> Hi Minye
Hi Minyen,
I'm Darwin, also a member of the Google Ads API team. I work with Carmela and
allow me to assist you here. I hope you are doing well today.
Please see my answer to your question below.
1.) So you're saying once I complete the app verification process, then I can
get a refresh token
Hi Carmela,
So you're saying once I complete the app verification process, then I can
get a refresh token that never expires?
To complete the verification process, I will need to input Application Home
Page and Application Privacy Policy, and also create a Youtube video for
demo. I am only usi
Problem: I'm using the *refresh token (I got it from the Oauth2.0
playground)* to get the* access token* using the POST method in POSTMAN. It
worked, however, after 7 days, it gives me an {'error': 'invalid_grant',
'error_description': 'Bad Request'}
I am trying to troubleshoot but I have so ma
Hi,
Thank you for your follow up.
You mentioned that you already created a new set of credentials and refresh
token and yet the issue persists. That said, could you confirm if :
You created your client ID and client secret by referring the steps mentioned
here
The refresh token was created by
Hello, Thank you for your reply.
However, I tried regenerating a new refresh token but I also got the same
error. I also tried regenerating a new client ID and client secret and then
regenerating a new refresh token but it also didn't work.
On Friday, August 6, 2021 at 7:17:34 PM UTC+3 adsapi w
Hi,
Thank you for reaching out to Google Ads API support. Refresh token support is
a general GCP issue for many API's, you may reach out to GCP support for
assistance.
With that being said you may want to try regenerating the refresh token. You
may also check this page about refresh token expi
I am not able to make API calls, I am getting this error:
google.auth.exceptions.RefreshError: ('invalid_grant: Bad Request',
{'error': 'invalid_grant', 'error_description': 'Bad Request'})
Although I am following exactly all the steps req
e ->
https://developers.google.com/adwords/api/docs/samples/python/remarketing
"Create and populate a user list"
It fails on this line (presumably the first time it tries to authenticate):
*result = user_list_service.mutate(operations)*
with:
*google.auth.exceptions.RefreshError: ('invalid_
*
Which seems healthy.
When I run the sample code from here
-> https://developers.google.com/adwords/api/docs/samples/python/remarketing
"Create and populate a user list"
It fails on this line (presumably the first time it tries to authenticate):
*result = user_list_service.mutate
Hi,
We have solved this issue.
As all of our clients link to our Adwords Account MCC, we always OAuth to
our MCC.
What we were doing is requesting a new OAuth refresh token every time we
setup a new client in our system and saved this refresh token against this
client - this meant that we
Hi,
Sorry I got the numbers mixed up.
13/33 *have* RefreshErrors.
{'id': 7781436429}
{'id': 2571805292}
{'id': 9558321396}
{'id': 5101096140}
{'id': 3305442630}
{'id': 7295155533}
{'id': 1904669782}
{'id': 9477072454}
{'id': 9838836942}
{'id': 1934329786}
{'id': 9871404976}
{'id': 4457413337}
{'
Hi,
Thanks for the email.
I have tried the curl command but still get the same issue.
We currently manage 33 adwords accounts.
13/33 have no RefreshErrors.
23/33 of these accounts have RefreshErrors.
We are using the same client_id and client_secret for all 33 accounts.
Its strange how the r
Hi Sanjay,
The "invalid_grant" error usually indicates that the access or refresh
token being passed in your request is incorrect or invalid. To verify that
your credentials are correct, you could also try the CURL request provided
below and see if you are able to generate the access tokens? If
I also read this here
(https://developers.google.com/identity/protocols/OAuth2InstalledApp#offline)
Note that there are limits on the number of refresh tokens that will be
> issued; one limit per client/user combination, and another per user across
> all clients. You should save refresh tokens
Hi,
We manage multiple adwords accounts and have been doing so for some time
now without seeing this issue before.
When we request a new access token with the refresh token we have saved for
a client:
HTTP METHOD: POST
HEADERS: 'content-type': 'application/x-www-form-urlencoded'
URI: https://a
16 matches
Mail list logo
