Error: [AuthorizationError.USER_PERMISSION_DENIED @ ; trigger:'']

[eric haberman]

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!

[Michael Cloonan (AdWords API Team)]

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, 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

[eric haberman]

Thanks Mike for the quick response!

Sorry for the confusion :/ 

"there is no link between the MCC account authenticated in the request and the client account specified in the headers."

Since I'm using my MCC account client ID (not a sub-client account), shouldn't it already be authorized?  The refresh token was generated for my MCC, using the MCC secret and client ID.

[eric haberman]

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:

[Michael Cloonan (AdWords API Team)]

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

[eric haberman]

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.