Exception says "An API exception has occurred. See ApiException and InnerException fields for more details."

[Oscar Martinez]

Hi, 

I get this error trying to get information about campaigns. I'm using one of the examples of the official .Net Library.

Looking for a similar post, I found this: 

https://groups.google.com/forum/#!msg/adwords-api/WOlH5z4-yDs/US4ZY-4QhlwJ

Answering what Takeshi Hagikura asked in the post reply:

Are you using a test account or a production account? 

Both, Production and Testing account.

Either way, please make sure you have accepted the terms&conditions for AdWords API.

Yes, I have.

If you use a production account, please make sure you have filled in the billing information.

Yes, I have. Production MCC Developer Token is pending approval.

Error message:

Failed to get campaigns. Exception says "An API exception has occurred. See ApiException and InnerException fields for more details."

What I get from OAuth2:

<add key='AuthorizationMethod' value='OAuth2' />

<add key='OAuth2ClientId' value='XXXXXXXXXXXXXXX' />

<add key='OAuth2ClientSecret' value='XXXXXXXXXX' />

<add key='OAuth2RefreshToken' value='XXXXXXXXXXX' />

Thank you, 

[Oscar Martinez]

More info... 

Debugging we find this error message:

[AuthorizationError.USER_PERMISSION_DENIED @ ; trigger:'<null>']

We find it in:

    protected virtual object[] MakeApiCall(string methodName, object[] parameters) {

      ErrorHandler errorHandler = CreateErrorHandler();

      while (true) {

        try {

          InitForCall(methodName, parameters);

          return base.Invoke(methodName, parameters);  //-> Here is the error

     ....

Thanks, 

[Ray Tsang (AdWords API Team)]

Oscar,

Most likely the user you used to login/authorize the OAuth 2.0 token does not have the permission to access the account.  Please double check and regenerate the token.

Thanks,

Ray

[Oscar Martinez]

Hi Ray, 

Thanks for your answer. Are you talking about regenerating the token in MCC? And, what account, Testing or my company's Production?

On Thursday, August 21, 2014 12:59:29 PM UTC-6, Oscar Martinez wrote:

[Anash P. Oommen (AdWords API Team)]

Hi Oscar,

No, AdWords API requires an OAuth2 access and refresh token to make calls to the account. If your current credentials cannot make calls to the desired account, you have to use one that has access to perform the required operation.

See the instructions on https://github.com/googleads/googleads-dotnet-lib/wiki/Using-OAuth2TokenGenerator to generate a new set of refresh and access tokens using a login email that has the right set of permissions.

Cheers,
Anash P. Oommen,
AdWords API Advisor.

[Oscar Martinez]

Hi Anash, 

Yes, we followed that process to get the XML lines for web.config. I will the redo the process and let you know what we get.

Thank you, 

On Thursday, August 21, 2014 12:59:29 PM UTC-6, Oscar Martinez wrote:

[Oscar Martinez]

We do it again... the result was the same error. We tried with Testing Account and Production Account.

Pdata: is it possible to know for this media why our Production Token continues being as "Pending Approval"?

Thank you, 

On Thursday, August 21, 2014 12:59:29 PM UTC-6, Oscar Martinez wrote:

[Anash P. Oommen (AdWords API Team)]

Hi Oscar,

Could you respond privately by using the "Reply to Author" option and provide the following details?

1. A request and response SOAP log for failed request.

2. The login email that you used to generate your refresh token?

I'll take a look and help figure out what may be wrong.

Cheers,
Anash P. Oommen,
AdWords API Advisor.

[Oscar Martinez]

Hi Anash, 

Last Friday I sent you the information about the SOAP log. I both cases, Test and Production accounts, we get the same SOAP log message.

Thank you. 

On Thursday, August 21, 2014 12:59:29 PM UTC-6, Oscar Martinez wrote:

[Anash P. Oommen (AdWords API Team)]

Hi Oscar,

I sent you a private response, could you reply to that email and provide the logs once more?

Thx,
Anash

[Oscar Martinez]

Done! I sent it by email.

On Thursday, August 21, 2014 12:59:29 PM UTC-6, Oscar Martinez wrote: