Re: [QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'New developers must use the Google Ads API.']

Hi Denis, It looks like you are using the upload offline conversions sample. The sample specifies that custom variable constants are optional: // Optional: Specify the conversion custom variable ID and value you want to // associate with the click conversion upload. private const

Re: [QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'New developers must use the Google Ads API.']

Thank you. So I was using the wrong library, that's why It wasn't working. I'm now using the code you suggested, and i successfully ran the example to get the campaigns from https://github.com/googleads/google-ads-php. Unfortunately when I run an UploadOfflineConversation, i can't pass the

Re: [QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'New developers must use the Google Ads API.']

Hi Denis, The AdWords API is no longer available for new users. Please use the new Google Ads API. Can you please confirm if you have had any specific issues with using the Ads API with your developer token? If you're having trouble getting started, can you let us know what stage you are

Re: QuotaCheckError.INVALID_TOKEN_HEADER

Hello, Based on what you said, I made a few changes to the documentation such as rewording the Sign Up page in the AdWords API (https://developers.google.com/adwords/api/docs/guides/signup) to make it more clear that new sign ups can only happen for the Google Ads API now. Thanks for taking

Re: [QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'New developers must use the Google Ads API.']

Hi Since you are implying that the issue come from the Authentication, I created a new token just now, and in the authentication process I chose to access both API, to test something new. (with option = 2) -> same issue 1st of June at 16:10 Sydney Time. -> time:

Re: QuotaCheckError.INVALID_TOKEN_HEADER

>> In that blog post, we say, "Any developers applying for a new developer token after today will only be given access to the Google Ads API. " Sorry I didn't answer right away. Thank you very much, we started working with the new documentation and now everything is fine. The two Google Ads API

Re: [QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'New developers must use the Google Ads API.']

Hi, I work with William and let me provide support to your concern. Could you confirm if the developer token was recently created and you've used it in API request of AdWords API? If yes, then new developer tokens can only be used with the Google Ads API. Existing developer tokens before the

Re: [QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'New developers must use the Google Ads API.']

I already look the error doc And I copy the token and same it in Googleads.yaml file property... Is there any solution to figure out the exactly is woung? BTW if you guys logs let me know. On Wednesday, 26 May 2021 at 22:03:41 UTC+5:30 adsapiforumadvisor wrote: > Hi 360Tech, > > Thank you

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'New developers must use the Google Ads API.How to check what the issue is?

Hi Sergey, Just to clarify, have you resolved the other errors mentioned in this thread and are currently blocked by the streaming error with message: "Streaming calls are not supported while using the REST transport"? If so I can try to help you find a solution, I just want to make sure

RE: [QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'New developers must use the Google Ads API.']

Hi 360Tech, Thank you for bringing this issue to our attention. As you will see here, when getting this error it shows that the developer token being used is either not correct or mistyped. We would suggest to make sure that any references to the token are correct as it is easy to mistype

Re: [QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'New developers must use the Google Ads API.']

Hello, My name is Matt and I work alongside Peter. Can you please provide us with the date that your developer token was created? Thanks, Matt Google Ads API Team Matt Google Ads API Team ref:_00D1U1174p._5004Q2HCemA:ref -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on

Re: [QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'New developers must use the Google Ads API.']

Hi, To clarify, I received the token, and tried to push an offline conversion. I didn't do anything else. So I guess I should wait for your feedback about this? Le lundi 24 mai 2021 à 13:13:14 UTC+10, adsapiforumadvisor a écrit : > Hi Denis, > > Thank you for reaching out to our API support

Re: QuotaCheckError.INVALID_TOKEN_HEADER

Hello, In April, we announced the sunset of the AdWords API (https://ads-developers.googleblog.com/2021/04/upgrade-to-google-ads-api-from-adwords.html). In that blog post, we say, "Any developers applying for a new developer token after today will only be given access to the Google Ads API. "

Re: QuotaCheckError.INVALID_TOKEN_HEADER

Hello, tried again - the error persists. We need this API, so we really look forward to your comments and recommendations. The developer token was created very recently (a few days ago) and did not touch the updates (April 22), which are mentioned in neighboring similar topics. понедельник,

RE: QuotaCheckError.INVALID_TOKEN_HEADER

Hello, I'll take a look and see if this error message is intended or not. I will provide an update as soon as I hear any updates. Regards, Anthony Anthony Google Ads API Team ref:_00D1U1174p._5004Q2HD5KB:ref -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog:

RE: [QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'New developers must use the Google Ads API.']

Hi Denis, Thank you for reaching out to our API support team. However, I had to delete your initial post as it contained the details of your logs. For further discussion on your logs, you may send the details using the Reply privately to author option, or email us directly via our

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'New developers must use the Google Ads API.How to check what the issue is?

Hello. What is the reason for this error? Streaming calls are not supported while using the REST transport. (0) /vendor/google/gax/src/Transport/HttpUnaryTransportTrait.php:137 #0: Google\ApiCore\Transport\RestTransport->throwUnsupportedException() суббота, 22 мая 2021 г. в 00:21:01 UTC+3,

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'New developers must use the Google Ads API.How to check what the issue is?

Hello - Thank you, 05.11.2021 This works with - https://developers.google.com/google-ads/api/docs/start пятница, 21 мая 2021 г. в 18:10:04 UTC+3, adsapiforumadvisor: > Hello - > > Can you clarify when the developer token you used for these queries was > created? I'm looking into it, but

RE: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'New developers must use the Google Ads API.How to check what the issue is?

Hello - Can you clarify when the developer token you used for these queries was created? I'm looking into it, but it's possible that, since the AdWords API deprecation notice was announced, we've placed limitations on the usage of the AdWords API for new developer tokens. Thanks, Ben Karl,

RE: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'New developers must use the Google Ads API.How to check what the issue is?

Hi, Thank you for reaching out to our API support team. However, I had to remove your initial post as it contained information of your entire logs. For future posts and further discussion on your logs, you may send these details using the Reply privately to author option or you may also opt to

Re: QuotaCheckError.INVALID_TOKEN_HEADER. How to check what the issue is?

Thank you so much Joyce! I'll do that and get back to you. On Tuesday, 12 July 2016 16:44:37 UTC+5:30, Joyce Lava wrote: > > Hi Manu, > > Thanks for the information. INVALID_TOKEN_HEADER > > >

Re: QuotaCheckError.INVALID_TOKEN_HEADER. How to check what the issue is?

Hi Manu, Thanks for the information. INVALID_TOKEN_HEADER error occurs when the developer token is not set on the request or it contains a typo. The cause may also be an incorrect namespace of

Re: QuotaCheckError.INVALID_TOKEN_HEADER. How to check what the issue is?

Hi Manu, Could you please provide the actual login email that was used when requesting developer token and the actual login email of the test manager account? Please make sure to use *Reply Privately to Author* when sending these information. Thanks and Regards, Joyce, AdWords API Team --

Re: QuotaCheckError.INVALID_TOKEN_HEADER with the PHP v201603 API provided examples

Hello, The INVALID_TOKEN_HEADER error is due to these reasons 1)developer token is not set on the request or it contains a typo. 2)The namespace of the headers in the request is not correct.

Re: QuotaCheckError.INVALID_TOKEN_HEADER with PHP

Hello, The problem is that you are using your email address instead of your developer token. If you are still having trouble, please reply to me directly and include your full SOAP request. Regards, Mike, AdWords API Team On Tuesday, December 9, 2014 5:08:09 AM UTC-5, Manuel Gómez wrote:

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Same problem here with the php 201209 lib. using TargetingIdeaService in sandbox is returning QuotaCheckError.INVALID_TOKEN_HEADER. We really need this solved as we cannot test / send to production our applications. On Wednesday, January 18, 2012 4:35:51 PM UTC+1, Sunil wrote: Hello, Since

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Hello Priya, I'll ask my colleague who is the author of the CSharp libraries to look into this issue for you. -Danial. Original Message Follows: From: Priya Gandhi pgan...@relevantads.com Subject: Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'??? Date

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Hello Priya, Are you trying to use the TargetingIdeaService by chance? This service will not provide meaningful results in the Sandbox and currently returns an error. -Danial, AdWords API Team. On Saturday, October 13, 2012 1:26:43 AM UTC+4, Priya Gandhi wrote: Hi, We are planning to

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Hi Danial, I am trying to run the *AdWords.Examples.CSharp.OAuth* application from the downloaded code and clicked the GetCampaigns button by providing one of our customerID. I have ENABLED OAuth2 through my account and received OAuth2ClientId and OAuth2ClientSecret for localhost. I have given

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Hi, We are planning to implement Adwords API and currently the sandbox testing was successful. I got OAuth2ClientId and OAuth2ClientSecret for the localhost by following the steps given in the link http://code.google.com/p/google-api-adwords-dotnet/wiki/UsingOAuth and started testing

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Hello, I was wondering if this was ever resolved? I have a .NET application that was working fine for months and downloading data every day. On June 13 it stopped working with the same error message. |||eye3-stackless title='AuthServer User Error INVALID_TOKEN_HEADER'/

Re: QuotaCheckError.INVALID_TOKEN_HEADER using Perl Examples

We are running Perl 5.8.8. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are

Re: QuotaCheckError.INVALID_TOKEN_HEADER using Perl Examples

If you perldoc HTTP::Status in your perl environment, it may not be as up to date as this http://search.cpan.org/~gaas/HTTP-Message-6.03/lib/HTTP/Status.pm. I am also running Perl 5.8.8, and i had to do this workaround. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our

Re: QuotaCheckError.INVALID_TOKEN_HEADER using Perl Examples

If you perldoc HTTP::Status in your perl environment, it may not be as up to date as this http://search.cpan.org/~gaas/HTTP-Message-6.03/lib/HTTP/Status.pm. I am also running Perl 5.8.8, and i had to do this workaround. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our

Re: QuotaCheckError.INVALID_TOKEN_HEADER using Perl Examples

I was able to update the HTTP::Status module and it eliminated those errors. Thanks for your help - I really appreciate it! Still not having any luck with the INVALID_TOKEN_HEADER issue. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group:

Re: QuotaCheckError.INVALID_TOKEN_HEADER using Perl Examples

Take a look at this blog post http://adwordsapi.blogspot.com/2011/11/action-required-developer-token.html -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api

Re: QuotaCheckError.INVALID_TOKEN_HEADER using Perl Examples

I read the article earlier. In the article it says We will be publishing updates to the example and utility code in the client libraries to reflect this change., so I figured the developer token would be passed correctly in the Google::Ads::AdWords module. Maybe this is a bad assumption? --

Re: QuotaCheckError.INVALID_TOKEN_HEADER using Perl Examples

In order to make any of the API calls you need to make the call on a Client object. You can define the client like this: my $client = Google::Ads::AdWords::Client-new({ version = 'v201109', email = 'login', password = 'password', developer_token = TOKEN,

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

HI Sunil, Yes, I believe this indicates that you are sending it successful. Best, - Eric -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Hi Alexander, We first communicated this change in November of last year, and then again about a week ago: http://adwordsapi.blogspot.com/2011/11/update2-developer-token-required-in.html http://googleadsdeveloper.blogspot.com/2012/01/developer-token-required-in-reports.html Sunil, Please make

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Eric, I'm using the latest v201109 Adwords API. Is there something else I should be using? Sunil On Jan 19, 8:12 am, Eric Koleda eric.kol...@google.com wrote: Hi Alexander, We first communicated this change in November of last year, and then again about a week ago:

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Using php, I have always had the developers token in the auth.ini, so why am I getting this message? On Jan 19, 3:12 pm, Eric Koleda eric.kol...@google.com wrote: Hi Alexander, We first communicated this change in November of last year, and then again about a week ago:

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Eric, I am using the v200109 API. I am sending the developer token. What else am I missing? Is there an email address I can reach you at? I am unable to download any client reports. Sunil On Jan 19, 8:58 am, Sunil su...@sweetspotmarketing.com wrote: Eric, I'm using the latest v201109

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

OK, uploaded the 2.7.2 library and that solved the issue. But why did I have to go through loads of stuff to find that out. Also, the idea of using a blog of all things to announce important updates is just daft. There has to be a better way. I just switch off with blog stuff it just gets lumped

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Hello, I am now getting a QuotaCheckError.ACCOUNT_INACTIVE error. Could this also be related to the developer token? Sunil On Jan 19, 9:57 am, opalepatrick ad...@patpatworks.com wrote: OK, uploaded the 2.7.2 library and that solved the issue. But why did I have to go through loads of stuff to

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

So, is the QuotaCheckError.ACCOUNT_INACTIVE error anything to do with the developer token? On Jan 19, 1:05 pm, Eric Koleda eric.kol...@google.com wrote: Hi opalepatrick, We're open to suggestions on how best to communicate this information. Sunil, v201109 is the version of the API you

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

I got the .Net library, made some code changes and when I tried to download the reports, I got the QuotaCheckError.ACCOUNT_INACTIVE error. Please help On Jan 19, 1:14 pm, Sunil su...@sweetspotmarketing.com wrote: So, is the QuotaCheckError.ACCOUNT_INACTIVE error anything to do with the

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Eric, The request header has the following information: {clientCustomerId: 7720483380 Content-Type: application/x-www-form-urlencoded Authorization: GoogleLogin auth=sometext returnMoneyInMicros: false developerToken: developertoken Please let me know whether the request header looks alright or

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Hi Sunil, This error indicates that the MCC account that owns your token is currently disabled. Please log into the account to resolve this. Best, - Eric -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

So, Eric, does this mean that I am sending the developer token successfully? On Jan 19, 3:08 pm, Eric Koleda eric.kol...@google.com wrote: Hi Sunil, This error indicates that the MCC account that owns your token is currently disabled.  Please log into the account to resolve this. Best, -

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

I am using the .Net API and we weren't using the developer token even though it should have been blocking us since November. I added it to our headers and things are working again via the .Net API. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

FWIW, I'm also seeing this (thought intermittently) as of this morning in v201101. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

I am connecting to the live API server. The strange part is 90% of my reports get downloaded successfully. However, on 10% of the reports, I get an QuotaCheckError.INVALID_TOKEN_HEADER error. Nothing changed in my code over the last several weeks. Why am I getting this error today? On Jan 18,

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

I suspect there was a server update yesterday related to dev_token headers : http://adwordsapi.blogspot.com/2011/11/update2-developer-token-required-in.html Most likely something else got broken during this update. Anyways a quick fix would be a retry mechanism, it works for us Alex --

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

I am already sending the developer token. I am able to download 90% of reports. But, I get an QuotaCheckError.INVALID_TOKEN_HEADER error on the 10% reports. On Jan 18, 11:19 am, Alexander Parij paris.a...@gmail.com wrote: I suspect there was a server update yesterday related to dev_token headers

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

We are seeing this too using the Ruby client library. Same symptoms, fails intermittently after downloading successfully from several accounts. On Jan 18, 11:32 am, Sunil su...@sweetspotmarketing.com wrote: I am already sending the developer token. I am able to download 90% of reports. But, I

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Now I am unable to download report even for a single account On Jan 18, 12:31 pm, rohit rohit.namjo...@gmail.com wrote: We are seeing this too using the Ruby client library. Same symptoms, fails intermittently after downloading successfully from several accounts. On Jan 18, 11:32 am,

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Yes , if before it could be solved by just re-trying now it's all gone nothing works at all. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Any update on this from Google? I am having the same exact problem. On Jan 18, 2:13 pm, Alexander Parij paris.a...@gmail.com wrote: Yes , if before it could be solved by just re-trying now it's all gone nothing works at all. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Hi All, As per the blog post Alexander linked to ( http://adwordsapi.blogspot.com/2011/11/update2-developer-token-required-in.html) developer tokens are now required for all report download requests. If you believe you are passing your developer token correctly please let us know what client

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

It's definitely developerToken related and they mention in this blog post http://adwordsapi.blogspot.com/2011/11/action-required-developer-token.html If your application fails to provide the developer token as an HTTP header after November 23rd, it will receive the error message

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

I am using AdwordsApi v201109 with .Net. On Jan 18, 5:21 pm, Eric Koleda eric.kol...@google.com wrote: Hi All, As per the blog post Alexander linked to (http://adwordsapi.blogspot.com/2011/11/update2-developer-token-requir...) developer tokens are now required for all report download

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Eric, I'm using python library 14.2.3 *** Outgoing SOAP ** ?xml version=1.0 encoding=UTF-8? SOAP-ENV:Envelope xmlns:SOAP-ENC=http://schemas.xmlsoap.org/soap/encoding/; xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/;

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Hi Alexander, The client library didn't start sending the developer token in the request until 15.0.4: http://code.google.com/p/google-api-ads-python/source/browse/trunk/adspygoogle/adwords/ChangeLog For everyone else, please ensure you are using the latest version of the client library.

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

I am using the latest dotnet library (I just downloaded it) and it's still giving me the same error. I am adding the developer token header. On Jan 18, 3:39 pm, Eric Koleda eric.kol...@google.com wrote: Hi Alexander, The client library didn't start sending the developer token in the request

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Never mind. It worked! I was adding it only to the report definition not the URL request. Thanks. On Jan 18, 3:42 pm, stepanian rstepan...@espinneret.com wrote: I am using the latest dotnet library (I just downloaded it) and it's still giving me the same error. I am adding the developer token

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Eric as you can see in the outgoing soap I do send developerToken with v14 -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Stepanian, How are you adding the developer token to the URL request? I am also using .Net library On Jan 18, 5:44 pm, stepanian rstepan...@espinneret.com wrote: Never mind. It worked! I was adding it only to the report definition not the URL request. Thanks. On Jan 18, 3:42 pm, stepanian

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Guys, I need some assistance. I am using the DownloadClientReport() method to download the ClientReports in .net : new ReportUtilities(user).DownloadClientReport(reportDefinitionId, false, filePath); I created the user object by: AdWordsUser user =

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

You need to do two things: 1) Make sure you are using the latest dotnet client library. 2) Add the developer token to both the report definition mutate operation and also to the report download operation. For the report download, I use the following code: string gZipPath

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Thanks Stepanian. Could you please tell me what's wrong with my code that I pasted above? On Jan 18, 6:30 pm, stepanian rstepan...@espinneret.com wrote: You need to do two things: 1) Make sure you are using the latest dotnet client library. 2) Add the developer token to both the report

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Eric , this is something that you should communicate before not after everything brakes down . Anyways upgrading to v15 is out of the question until we properly test it. I had to patch v14.2.3 to add developerToken header in this particular call to download the report for anyone in the

Re: QuotaCheckError.INVALID_TOKEN_HEADER @ ; trigger:'null'???

Eric, I need your help with figuring out the issue I am having. Please Sunil On Jan 18, 7:09 pm, Alexander Parij paris.a...@gmail.com wrote: Eric , this is something that you should communicate before  not after everything brakes down . Anyways upgrading to v15 is out of the question

Re: QuotaCheckError.INVALID_TOKEN_HEADER

Hi, I don't have a timeframe with me right now, but it typically happens in a week or max 2. Cheers, Anash P. Oommen, AdWords API Advisor. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com

Re: QuotaCheckError.INVALID_TOKEN_HEADER

Ok thanks. Do you know when the next server update is going to take place? -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

Re: QuotaCheckError.INVALID_TOKEN_HEADER

Hi, We have a known issue at our end that causes some of our users to get an QuotaCheckError.INVALID_TOKEN_HEADER when downloading reports. The reports team has fixed this issue at their end, the fix should be on our servers during the next server update. Cheers, Anash P. Oommen, AdWords API

Re: QuotaCheckError.INVALID_TOKEN_HEADER error

That was a temporary error. All working now. I did not save the SOAP request, the response is in previous post and includes request id. Henri On Jun 16, 5:23 am, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi Henri, Can you post the SOAP request and response xmls for this

Re: QuotaCheckError.INVALID_TOKEN_HEADER error

Hi Henri, Can you post the SOAP request and response xmls for this request? Thanks, Anash P. Oommen, AdWords API Team On Jun 16, 12:52 am, h805 halta...@rain.org wrote: We started receiving this error after reinitializing our sandbox. The trigger is nowhere to be found in our request. Any