AI-generated Key Takeaways
-
The content provides an enumeration of possible authorization errors.
-
Each enum value describes a specific type of authorization issue that can occur.
-
Examples of errors include permission denials, token issues, project access problems, and account status limitations.
Enum describing possible authorization errors.
| Enums | |
|---|---|
|
Enum unspecified. |
|
The received error code is not known in this version. |
|
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. Learn more at https://developers.google.com/google-ads/api/docs/concepts/call-structure#cid |
|
The developer token is not on the allow-list. |
|
The developer token is not allowed with the project sent in the request. |
|
The Google Cloud project sent in the request does not have permission to access the api. |
|
Authorization of the client failed. |
|
The user does not have permission to perform this action (for example, ADD, UPDATE, REMOVE) on the resource or call a method. |
|
Signup not complete. |
|
The customer account can't be accessed because it is not yet enabled or has been deactivated. |
|
The developer must sign the terms of service. They can be found here: ads.google.com/aw/apicenter |
|
The developer token is only approved for use with test accounts. To access non-test accounts, apply for Basic or Standard access. |
|
The login customer specified does not have access to the account specified, so the request is invalid. |
|
The developer specified does not have access to the service. |
|
The customer (or login customer) isn't in Google Ads. It belongs to another ads system. |
|
The developer does not have access to the metrics queried. |
|
The Google Cloud project is not under the required organization. |
|
The user does not have permission to perform this action on the resource or method because the Google Ads account is suspended. |