subject:"Re\: cannot access adwords services via test account using production developers token."

Re: cannot access adwords services via test account using production developers token.

2018-10-08 Thread 'Dannison Yao (AdWords API Team)' via AdWords API and Google Ads API Forum

Hi Parvathy,

Could you provide your clientId and clientSecret via *Reply privately to 
author* so I could further investigate this issue?

Regards,
Dannison
AdWords API Team

On Monday, October 8, 2018 at 8:54:14 PM UTC+8, Parvathy H wrote:
>
> Hi,
> Thank you for the advice.
>
> I am calling a service of adwords in this way:
>
> let campaignCriterionService = user.getService(service, config.version);
>  
> So the service returned in the user.getService method is as follows:
>
>  {
>
>- "credentials" : -{
>   - "developerToken" : ,
>   - "userAgent" : ABC,
>   - "clientCustomerId" : 7799076323,
>   - "client_id" : xxexample.googleapis.com,
>   - "client_secret" : xx,
>   - "refresh_token" : xxx,
>   - "access_token" : 
>   
>   - ,
>   - "token_expiry" : 2018-10-08T11:03:59.453Z
>},
>- "auth" : -{
>   - "credentials" : -{
>  - "developerToken" :    ,
>  - "userAgent" : ABC,
>  - "clientCustomerId" : 7799076323,
>  - "client_id" :  xxexample.googleapis.com  ,
>  - "client_secret" : xx,
>  - "refresh_token" : 
>  xxx,
>  - "access_token" : 
>  
> xx
>  - xx,
>  - "token_expiry" : 2018-10-08T11:03:59.453Z
>   },
>   - "oauth2Client" : -{
>  - "transporter" : -{
> },
>  - "clientId_" : 
>  
> xxx.apps.googleusercontent.com
>  ,
>  - "clientSecret_" : ,
>  - "opts" : -{
> },
>  - "credentials" : -{
> - "developerToken" : xx,
> - "userAgent" : IABC,
> - "clientCustomerId" : 7799076323,
> - "client_id" : 
> 
> .apps.googleusercontent.com
> ,
> - "client_secret" : ,
> - "refresh_token" : xx,
> - 
> "access_token" 
> :x
> - xxx,
> - "token_expiry" : 2018-10-08T11:03:59.453Z
>  }
>   }
>},
>- "serviceDescriptor" : -{
>   - "xmlns" : https://adwords.google.com/api/adwords/cm/v201802,
>   - "wsdl" : 
>   
> https://adwords.google.com/api/adwords/cm/v201802/LocationCriterionService?wsdl
>   ,
>   - "methods" : -[
>  - get,
>  - query
>   ]
>}
>
> }
>
> Here i provided *oauth2Client  manually in the serice return.**But still 
> i get the same *Error: soap:Client: 
> [AuthenticationError.OAUTH_TOKEN_INVALID @ ; trigger:''] error.
>
> On Sat, Sep 29, 2018 at 11:07 AM Parvathy H  
> wrote:
>
>> Hi,
>>
>> I tried to access service by giving the clent id ,secret_id and refresh 
>> token of Test manager account email address.
>> the production mcc email address is : anil.ku...@iinerds.com
>> The test manager account email address is :parvathyhku...@gmail.com
>>
>> The soap logs is as given below :
>>
>> { Error: soap:Client: [AuthenticationError.OAUTH_TOKEN_INVALID @ ; 
>> trigger:'']
>> at finish 
>> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\wsdl.js:1518:21)
>> at WSDL.xmlToObject 
>> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\wsdl.js:1501:10)
>> at parseSync 
>> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\client.js:368:23)
>> at 
>> C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\client.js:361:14
>> at Request._callback 
>> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\http.js:117:5)
>> at Request.self.callback 
>> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\request\request.js:186:22)
>> at emitTwo (events.js:126:13)
>> at Request.emit (events.js:214:7)
>> at Request. 
>> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\request\request.js:1163:10)
>> at emitOne (events.js:116:13)
>> at Request.emit (events.js:211:7)
>> at IncomingMessage. 
>>

Re: cannot access adwords services via test account using production developers token.

2018-10-08 Thread Parvathy H

Hi,
Thank you for the advice.

I am calling a service of adwords in this way:

let campaignCriterionService = user.getService(service, config.version);

So the service returned in the user.getService method is as follows:

 {

   - "credentials" : -{
  - "developerToken" : ,
  - "userAgent" : ABC,
  - "clientCustomerId" : 7799076323,
  - "client_id" : xxexample.googleapis.com,
  - "client_secret" : xx,
  - "refresh_token" : xxx,
  - "access_token" :
  
  - ,
  - "token_expiry" : 2018-10-08T11:03:59.453Z
   },
   - "auth" : -{
  - "credentials" : -{
 - "developerToken" :    ,
 - "userAgent" : ABC,
 - "clientCustomerId" : 7799076323,
 - "client_id" :  xxexample.googleapis.com  ,
 - "client_secret" : xx,
 - "refresh_token" : xxx
 ,
 - "access_token" :
 xx
 - xx,
 - "token_expiry" : 2018-10-08T11:03:59.453Z
  },
  - "oauth2Client" : -{
 - "transporter" : -{
},
 - "clientId_" :
 xxx.apps.googleusercontent.com
 ,
 - "clientSecret_" : ,
 - "opts" : -{
},
 - "credentials" : -{
- "developerToken" : xx,
- "userAgent" : IABC,
- "clientCustomerId" : 7799076323,
- "client_id" :
.apps.googleusercontent.com
,
- "client_secret" : ,
- "refresh_token" : xx,
-
"access_token"
:x
- xxx,
- "token_expiry" : 2018-10-08T11:03:59.453Z
 }
  }
   },
   - "serviceDescriptor" : -{
  - "xmlns" : https://adwords.google.com/api/adwords/cm/v201802,
  - "wsdl" :
  
https://adwords.google.com/api/adwords/cm/v201802/LocationCriterionService?wsdl
  ,
  - "methods" : -[
 - get,
 - query
  ]
   }

}

Here i provided *oauth2Client  manually in the serice return.**But still i
get the same *Error: soap:Client: [AuthenticationError.OAUTH_TOKEN_INVALID
@ ; trigger:''] error.

On Sat, Sep 29, 2018 at 11:07 AM Parvathy H  wrote:

> Hi,
>
> I tried to access service by giving the clent id ,secret_id and refresh
> token of Test manager account email address.
> the production mcc email address is : anil.ku...@iinerds.com
> The test manager account email address is :parvathyhku...@gmail.com
>
> The soap logs is as given below :
>
> { Error: soap:Client: [AuthenticationError.OAUTH_TOKEN_INVALID @ ;
> trigger:'']
> at finish
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\wsdl.js:1518:21)
> at WSDL.xmlToObject
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\wsdl.js:1501:10)
> at parseSync
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\client.js:368:23)
> at
> C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\client.js:361:14
> at Request._callback
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\http.js:117:5)
> at Request.self.callback
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\request\request.js:186:22)
> at emitTwo (events.js:126:13)
> at Request.emit (events.js:214:7)
> at Request.
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\request\request.js:1163:10)
> at emitOne (events.js:116:13)
> at Request.emit (events.js:211:7)
> at IncomingMessage.
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\request\request.js:1085:12)
> at Object.onceWrapper (events.js:313:30)
> at emitNone (events.js:111:20)
> at IncomingMessage.emit (events.js:208:7)
> at endReadableNT (_stream_readable.js:1064:12)
> at _combinedTickCallback (internal/process/next_tick.js:138:11)
> at process._tickDomainCallback (internal/process/next_tick.js:218:9)
>   root: { Envelope: { Header: [Object], Body: [Object] } },
>   response:
>

Re: cannot access adwords services via test account using production developers token.

2018-09-30 Thread 'Dannison Yao (AdWords API Team)' via AdWords API and Google Ads API Forum

Hi Parvathy,

I have to delete your previous reply as it contains sensitive information. 
Please see below your reply with the masked sensitive information.

I tried to access service by giving the clent id ,secret_id and refresh 
token of Test manager account email address.
the production mcc email address is : anil.ku...@iinerds.com
The test manager account email address is :parvathyhku...@gmail.com

The soap logs is as given below :

{ Error: soap:Client: [AuthenticationError.OAUTH_TOKEN_INVALID @ ; 
trigger:'']
at finish (C:\Parvathy\devSupernova\supernova-channel-integrator-parva
thy\channel-integrator\node_modules\soap\lib\wsdl.js:1518:21)
at WSDL.xmlToObject (C:\Parvathy\devSupernova\supe
rnova-channel-integrator-parvathy\channel-integrator\node_
modules\soap\lib\wsdl.js:1501:10)
at parseSync (C:\Parvathy\devSupernova\supernova-channel-integrator-
parvathy\channel-integrator\node_modules\soap\lib\client.js:368:23)
at C:\Parvathy\devSupernova\supernova-channel-integrator-parvat
hy\channel-integrator\node_modules\soap\lib\client.js:361:14
at Request._callback (C:\Parvathy\devSupernova\supe
rnova-channel-integrator-parvathy\channel-integrator\node_
modules\soap\lib\http.js:117:5)
at Request.self.callback (C:\Parvathy\devSupernova\supe
rnova-channel-integrator-parvathy\channel-integrator\node_
modules\request\request.js:186:22)
at emitTwo (events.js:126:13)
at Request.emit (events.js:214:7)
at Request. (C:\Parvathy\devSupernova\supe
rnova-channel-integrator-parvathy\channel-integrator\node_
modules\request\request.js:1163:10)
at emitOne (events.js:116:13)
at Request.emit (events.js:211:7)
at IncomingMessage. (C:\Parvathy\devSupernova\supe
rnova-channel-integrator-parvathy\channel-integrator\node_
modules\request\request.js:1085:12)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:111:20)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickDomainCallback (internal/process/next_tick.js:218:9)
  root: { Envelope: { Header: [Object], Body: [Object] } },
  response:
   IncomingMessage {
 _readableState:
  ReadableState {
objectMode: false,
highWaterMark: 16384,
buffer: [Object],
length: 0,
pipes: null,
pipesCount: 0,
flowing: true,
ended: true,
endEmitted: true,
reading: false,
sync: false,
needReadable: false,
emittedReadable: false,
readableListening: false,
resumeScheduled: false,
destroyed: false,
defaultEncoding: 'utf8',
awaitDrain: 0,
readingMore: false,
decoder: null,
encoding: null },
 readable: false,
 domain: null,
 _events:
  { end: [Array],
close: [Array],
data: [Function],
error: [Function] },
 _eventsCount: 4,
 _maxListeners: undefined,
 socket:
  TLSSocket {
_tlsOptions: [Object],
_secureEstablished: true,
_securePending: false,
_newSessionPending: false,
_controlReleased: true,
_SNICallback: null,
servername: null,
npnProtocol: false,
alpnProtocol: false,
authorized: true,
authorizationError: null,
encrypted: true,
_events: [Object],
_eventsCount: 10,
connecting: false,
_hadError: false,
_handle: null,
_parent: null,
_host: 'adwords.google.com',
_readableState: [Object],
readable: false,
domain: null,
_maxListeners: undefined,
_writableState: [Object],
writable: false,
allowHalfOpen: false,
_bytesDispatched: 1740,
_sockname: null,
_pendingData: null,
_pendingEncoding: '',
server: undefined,
_server: null,
ssl: null,
_requestCert: true,
_rejectUnauthorized: true,
parser: null,
_httpMessage: [Object],
read: [Function],
_consuming: true,
write: [Function: writeAfterFIN],
_idleNext: null,
_idlePrev: null,
_idleTimeout: -1,
[Symbol(asyncId)]: 538,
[Symbol(bytesRead)]: 1559 },
 connection:
  TLSSocket {
_tlsOptions: [Object],
_secureEstablished: true,
_securePending: false,
_newSessionPending: false,
_controlReleased: true,
_SNICallback: null,
servername: null,
npnProtocol: false,
alpnProtocol: false,
authorized: true,
authorizationError: null,
encrypted: true,
_events: [Object],
_eventsCount: 10,
connecting: false,
_hadError: false,
_handle: null,
_parent: null,
_host: 'adwords.google.com',
_readableState: [Object],
readable: false,

Re: cannot access adwords services via test account using production developers token.

2018-09-30 Thread 'Dannison Yao (AdWords API Team)' via AdWords API and Google Ads API Forum

Hi Nikhil,

I can see that you have posted a new thread 

 with 
regards to your issue in which I have responded. You could refer to that 
thread for better communication.

Regards,
Dannison
AdWords API Team

On Saturday, September 29, 2018 at 4:43:13 AM UTC+8, nikhil almeida wrote:
>
>
> Does the API credentials need to be set up by the same person who has 
> created the Production MCC account?
>
> I am a developer who has access to the production MCC account, who set up 
> the test MCC accounts and who has set up the credentials in Google Cloud. 
> And I still get the 'OAuthTokenInvalid Error'
>
> NIkhil
>
>
>
> On Thursday, September 27, 2018 at 9:21:25 PM UTC-7, parva...@iinerds.com 
> wrote:
>>
>> Hi,
>>
>> I tried to create campaign using a test account:
>> The credential details are given as below:
>>
>>
>  
>
>> 1.The client id, secret id and refresh token used was of *Production MCC 
>> account*.
>> 2.The developer token used is of the same *Production MCC account* mentioned 
>> above which is in *pending approval*.
>> 3.The *client_customer_id *to which the campaign needs to be pushed is 
>> the "client customer id" of the *test account in test manager account.*
>>
>>
>> But after doing all this still when accessing the 
>> *LocationCriterionService*  i am getting the following error:
>>
>> { Error: soap:Client: [AuthenticationError.*OAUTH_TOKEN_INVALID* @ ; 
>> trigger:'']
>> at finish 
>> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\wsdl.js:1518:21)
>> at WSDL.xmlToObject 
>> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\wsdl.js:1501:10)
>> at parseSync 
>> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\client.js:368:23)
>> at 
>> C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\client.js:361:14
>> at Request._callback 
>> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\http.js:117:5)
>> at Request.self.callback 
>> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\request\request.js:186:22)
>> at emitTwo (events.js:126:13)
>> at Request.emit (events.js:214:7)
>> at Request. 
>> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\request\request.js:1163:10)
>> at emitOne (events.js:116:13)
>> at Request.emit (events.js:211:7)
>> at IncomingMessage. 
>> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\request\request.js:1085:12)
>> at Object.onceWrapper (events.js:313:30)
>> at emitNone (events.js:111:20)
>> at IncomingMessage.emit (events.js:208:7)
>> at endReadableNT (_stream_readable.js:1064:12)
>> at _combinedTickCallback (internal/process/next_tick.js:138:11)
>> at process._tickDomainCallback (internal/process/next_tick.js:218:9)
>>
>>
>> Thank you
>>
>>
>>
>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/db916762-acd5-4b7d-8b45-a71477187ee9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: cannot access adwords services via test account using production developers token.

2018-09-28 Thread nikhil almeida


Does the API credentials need to be set up by the same person who has 
created the Production MCC account?

I am a developer who has access to the production MCC account, who set up 
the test MCC accounts and who has set up the credentials in Google Cloud. 
And I still get the 'OAuthTokenInvalid Error'

NIkhil



On Thursday, September 27, 2018 at 9:21:25 PM UTC-7, parva...@iinerds.com 
wrote:
>
> Hi,
>
> I tried to create campaign using a test account:
> The credential details are given as below:
>
>
 

> 1.The client id, secret id and refresh token used was of *Production MCC 
> account*.
> 2.The developer token used is of the same *Production MCC account* mentioned 
> above which is in *pending approval*.
> 3.The *client_customer_id *to which the campaign needs to be pushed is 
> the "client customer id" of the *test account in test manager account.*
>
>
> But after doing all this still when accessing the 
> *LocationCriterionService*  i am getting the following error:
>
> { Error: soap:Client: [AuthenticationError.*OAUTH_TOKEN_INVALID* @ ; 
> trigger:'']
> at finish 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\wsdl.js:1518:21)
> at WSDL.xmlToObject 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\wsdl.js:1501:10)
> at parseSync 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\client.js:368:23)
> at 
> C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\client.js:361:14
> at Request._callback 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\http.js:117:5)
> at Request.self.callback 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\request\request.js:186:22)
> at emitTwo (events.js:126:13)
> at Request.emit (events.js:214:7)
> at Request. 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\request\request.js:1163:10)
> at emitOne (events.js:116:13)
> at Request.emit (events.js:211:7)
> at IncomingMessage. 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\request\request.js:1085:12)
> at Object.onceWrapper (events.js:313:30)
> at emitNone (events.js:111:20)
> at IncomingMessage.emit (events.js:208:7)
> at endReadableNT (_stream_readable.js:1064:12)
> at _combinedTickCallback (internal/process/next_tick.js:138:11)
> at process._tickDomainCallback (internal/process/next_tick.js:218:9)
>
>
> Thank you
>
>
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/402684c3-4c39-4a05-9278-8bd0b091d425%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: cannot access adwords services via test account using production developers token.

2018-09-28 Thread parvathy . h



On Friday, September 28, 2018 at 9:51:25 AM UTC+5:30, parva...@iinerds.com 
wrote:
>
> Hi,
>
> I tried to create campaign using a test account:
> The credential details are given as below:
>
> 1.The client id, secret id and refresh token used was of *Production MCC 
> account*.
> 2.The developer token used is of the same *Production MCC account* mentioned 
> above which is in *pending approval*.
> 3.The *client_customer_id *to which the campaign needs to be pushed is 
> the "client customer id" of the *test account in test manager account.*
>
>
> But after doing all this still when accessing the 
> *LocationCriterionService*  i am getting the following error:
>
> { Error: soap:Client: [AuthenticationError.*OAUTH_TOKEN_INVALID* @ ; 
> trigger:'']
> at finish 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\wsdl.js:1518:21)
> at WSDL.xmlToObject 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\wsdl.js:1501:10)
> at parseSync 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\client.js:368:23)
> at 
> C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\client.js:361:14
> at Request._callback 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\http.js:117:5)
> at Request.self.callback 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\request\request.js:186:22)
> at emitTwo (events.js:126:13)
> at Request.emit (events.js:214:7)
> at Request. 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\request\request.js:1163:10)
> at emitOne (events.js:116:13)
> at Request.emit (events.js:211:7)
> at IncomingMessage. 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\request\request.js:1085:12)
> at Object.onceWrapper (events.js:313:30)
> at emitNone (events.js:111:20)
> at IncomingMessage.emit (events.js:208:7)
> at endReadableNT (_stream_readable.js:1064:12)
> at _combinedTickCallback (internal/process/next_tick.js:138:11)
> at process._tickDomainCallback (internal/process/next_tick.js:218:9)
>
>
> Thank you
>
>
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/8a6d8c6f-961a-4c8a-bb62-8f6a0ddfac61%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: cannot access adwords services via test account using production developers token.

2018-09-28 Thread parvathy . h



On Friday, September 28, 2018 at 9:51:25 AM UTC+5:30, parva...@iinerds.com 
wrote:
>
> Hi,
>
> I tried to create campaign using a test account:
> The credential details are given as below:
>
> 1.The client id, secret id and refresh token used was of *Production MCC 
> account*.
> 2.The developer token used is of the same *Production MCC account* mentioned 
> above which is in *pending approval*.
> 3.The *client_customer_id *to which the campaign needs to be pushed is 
> the "client customer id" of the *test account in test manager account.*
>
>
> But after doing all this still when accessing the 
> *LocationCriterionService*  i am getting the following error:
>
> { Error: soap:Client: [AuthenticationError.*OAUTH_TOKEN_INVALID* @ ; 
> trigger:'']
> at finish 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\wsdl.js:1518:21)
> at WSDL.xmlToObject 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\wsdl.js:1501:10)
> at parseSync 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\client.js:368:23)
> at 
> C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\client.js:361:14
> at Request._callback 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\http.js:117:5)
> at Request.self.callback 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\request\request.js:186:22)
> at emitTwo (events.js:126:13)
> at Request.emit (events.js:214:7)
> at Request. 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\request\request.js:1163:10)
> at emitOne (events.js:116:13)
> at Request.emit (events.js:211:7)
> at IncomingMessage. 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\request\request.js:1085:12)
> at Object.onceWrapper (events.js:313:30)
> at emitNone (events.js:111:20)
> at IncomingMessage.emit (events.js:208:7)
> at endReadableNT (_stream_readable.js:1064:12)
> at _combinedTickCallback (internal/process/next_tick.js:138:11)
> at process._tickDomainCallback (internal/process/next_tick.js:218:9)
>
>
> Thank you
>
>
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/69ee51ff-e81c-4f6b-b86a-b77f8e3de897%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: cannot access adwords services via test account using production developers token.

2018-09-28 Thread 'Dannison Yao (AdWords API Team)' via AdWords API and Google Ads API Forum

Hi,

The OAUTH_ 

TOKEN_INVALID 

 error 
means the OAuth access token in the header is not valid. Make sure you are 
using the correct token associated for your account. You can use the OAuth2 
Credentials generated using an email address which has access to your Test 
Manager Account and not the Production MCC account when doing a service 
call.

Once you applied the correct OAuth2 Credentials in making a request to your 
test client account, and still, this error persists, then kindly provide 
your complete SOAP request and response logs as well as the email address 
of your API user via *Reply privately to author *so I can further 
investigate.

Regards,
Dannison
AdWords API Team

On Friday, September 28, 2018 at 12:21:25 PM UTC+8, parvath...@iinerds.com 
wrote:
>
> Hi,
>
> I tried to create campaign using a test account:
> The credential details are given as below:
>
> 1.The client id, secret id and refresh token used was of *Production MCC 
> account*.
> 2.The developer token used is of the same *Production MCC account* mentioned 
> above which is in *pending approval*.
> 3.The *client_customer_id *to which the campaign needs to be pushed is 
> the "client customer id" of the *test account in test manager account.*
>
>
> But after doing all this still when accessing the 
> *LocationCriterionService*  i am getting the following error:
>
> { Error: soap:Client: [AuthenticationError.*OAUTH_TOKEN_INVALID* @ ; 
> trigger:'']
> at finish 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\wsdl.js:1518:21)
> at WSDL.xmlToObject 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\wsdl.js:1501:10)
> at parseSync 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\client.js:368:23)
> at 
> C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\client.js:361:14
> at Request._callback 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\soap\lib\http.js:117:5)
> at Request.self.callback 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\request\request.js:186:22)
> at emitTwo (events.js:126:13)
> at Request.emit (events.js:214:7)
> at Request. 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\request\request.js:1163:10)
> at emitOne (events.js:116:13)
> at Request.emit (events.js:211:7)
> at IncomingMessage. 
> (C:\Parvathy\devSupernova\supernova-channel-integrator-parvathy\channel-integrator\node_modules\request\request.js:1085:12)
> at Object.onceWrapper (events.js:313:30)
> at emitNone (events.js:111:20)
> at IncomingMessage.emit (events.js:208:7)
> at endReadableNT (_stream_readable.js:1064:12)
> at _combinedTickCallback (internal/process/next_tick.js:138:11)
> at process._tickDomainCallback (internal/process/next_tick.js:218:9)
>
>
> Thank you
>
>
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/48b1a623-010e-4cec-99d7-bcdc61416a27%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: cannot access adwords services via test account using production developers token.

Re: cannot access adwords services via test account using production developers token.

Re: cannot access adwords services via test account using production developers token.

Re: cannot access adwords services via test account using production developers token.

Re: cannot access adwords services via test account using production developers token.

Re: cannot access adwords services via test account using production developers token.

Re: cannot access adwords services via test account using production developers token.

Re: cannot access adwords services via test account using production developers token.

8 matches

Site Navigation

Mail list logo

Footer information