Thanks Mike!  

I actually resolved the issue, the access_token header was not being sent - 
when I updated the library one of the files was locked and not overwritten, 
so it was using an older version file to send the request.

On Friday, November 21, 2014 8:51:41 AM UTC-6, Michael Cloonan (AdWords API 
Team) wrote:
>
> Hello Eric,
>
> Are you able to make successful calls to client accounts of that MCC? You 
> could try generating a new refresh token for the MCC you're trying to use, 
> ensuring that you're logged in as that MCC, which may resolve the issue. 
> Maybe the refresh token you're using is from some other account.
>
> Regards,
> Mike, AdWords API Team
>
> On Thursday, November 20, 2014 3:06:05 PM UTC-5, eric haberman wrote:
>>
>> Mike it appears that my MCC account cannot access my MCC account :)
>>
>> Or am I missing a step where I need to authorize my MCC client ID with 
>> the same accounts developer and refresh tokens?
>>
>> If so, any idea how to go about doing that?
>>
>> Thanks!
>>
>> On Thursday, November 20, 2014 1:25:16 PM UTC-6, Michael Cloonan (AdWords 
>> API Team) wrote:
>>>
>>> Hello,
>>>
>>> You shouldn't need to generate a new refresh token to upgrade to a new 
>>> version of the API. Your existing refresh token should continue to work.
>>>
>>> As seen on our common errors page 
>>> <https://developers.google.com/adwords/api/docs/common-errors#AuthorizationError.USER_PERMISSION_DENIED>,
>>>  
>>> this error message means that the MCC you're authenticating as isn't linked 
>>> to the client account against which you're trying to operate, meaning that 
>>> you don't have permissions to act on that account. Please make sure that 
>>> your refresh token is linked to the correct MCC account, and that that MCC 
>>> account is linked to the account you're trying to use.
>>>
>>> Regards,
>>> Mike, AdWords API Team
>>>
>>> On Thursday, November 20, 2014 2:09:33 PM UTC-5, eric haberman wrote:
>>>>
>>>> Hello,
>>>>
>>>> I *thought* that I was all ready for the new API sunset, but apparently 
>>>> not.
>>>>
>>>> Using my MCC account, a new refresh token, and the clientID for my MCC 
>>>> account I'm getting this error when instantiating the user object (PHP 
>>>> library)
>>>>
>>>> Error: [AuthorizationError.USER_PERMISSION_DENIED @ ; trigger:'']
>>>>
>>>> Why would my MCC account be denied from accessing the API?
>>>>
>>>> Thanks for any help you can provide!
>>>>
>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords 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 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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/69a1d6f9-3157-4112-8b15-1d141b51316b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to