Programme access via request from MCC

[Mike]

Hi All,

we use Ads API V11 and download campaign information by standard. If the customer sends us an invitation to access the account and we confirm this, everything works fine.

The problem occurs if we request access via MMC and the customer confirms the request. We get access as administrators, we can set everything up via the web, but when we programmatically access it returns an error that we don't have access. In both cases we use the same account ID where we want to access.

I would be grateful for any advice on how to solve this problem.

{
  "StatusCode": 7,
  "Details": "The caller does not have permission",
  "RequestId": "64Kw0QNyzbkpfT37jGY0gQ",
  "Failure": {
    "errors": [
      {
        "errorCode": {
          "authorizationError": "USER_PERMISSION_DENIED"
        },
        "message": "User doesn't have permission to access customer. Note: If you're accessing a client customer, the manager's customer id must be set in the 'login-customer-id' header. See https://developers.google.com/google-ads/api/docs/concepts/call-structure#cid"
      }
    ],
    "requestId": "64Kw0QNyzbkpfT37jGY0gQ"
  }
}

[Google Ads API Forum Advisor]

Hi Mike,

Thank you for raising this concern to the Google Ads API support team.

With regards to your concern, I understand that you have encountered the USER_PERMISSION_DENIED error. This error means the authorized customer does not have access to the operating customer. Its common cause is when authenticating as a user with access to a manager account but not specifying login-customer-id in the request. To prevent this kind of error, I would suggest specifying the login-customer-id as the manager account ID without hyphens (-). Client libraries have built in support for this, or see our guide. Also, please make sure that the user / email address you used to generate the credentials indeed has access to the account specified in your request.

If the error persists, you may provide the complete request and response logs with request ID and request header generated on your end and the user / email address you used in authentication for further investigation. You can provide it via Reply privately to author option. If this option is not available, then send it instead on this email address googleadsa...@google.com.

Regards,

Carmela Google Ads API Team

ref:_00D1U1174p._5004Q2gjFTg:ref

[Mike]

Thank you Carmela for your reply and guidance. The link with the description to the prolinked account helped us and the download now works through the MCC account as well.