Authorize Requests
Stay organized with collections
Save and categorize content based on your preferences.
When your application requests private data, the request must be authorized by an authenticated user who has access to that data.
When your application requests public data, the request doesn't need to be authorized, but does need to be accompanied by an identifier, such as an API key.
Your application needs to identify itself every time it sends a request to
the Google Ad Experience Report API, by including an API key
with each
request.
Acquiring and using an API key
Get a Key
Or create one in the Credentials page
.
After you have an API key, your application can append the query parameter key= yourAPIKey
to all request URLs.
The API key is safe for embedding in URLs; it doesn't need any encoding.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License
, and code samples are licensed under the Apache 2.0 License
. For details, see the Google Developers Site Policies
. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-28 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[[["\u003cp\u003eApplications requesting private data require authorization from an authenticated user with data access.\u003c/p\u003e\n"],["\u003cp\u003ePublic data requests do not need authorization but require an identifier like an API key.\u003c/p\u003e\n"],["\u003cp\u003eAll requests to the Google Ad Experience Report API must include an API key for application identification.\u003c/p\u003e\n"],["\u003cp\u003eAPI keys can be obtained or created through the provided links and used as a query parameter in request URLs.\u003c/p\u003e\n"]]],["Applications interacting with the Google Ad Experience Report API must include an identifier with each request. For private data, user authorization is required. For public data, an API key suffices. To obtain an API key, users can get a key or create one on the Credentials page. Once obtained, the key should be appended to all request URLs using the `key=` parameter. The API key can be directly embedded and requires no encoding.\n"],null,["When your application requests private data, the request must be authorized by an authenticated user who has access to that data.\n\nWhen your application requests public data, the request doesn't need to be authorized, but does need to be accompanied by an identifier, such as an API key.\n\nYour application needs to identify itself every time it sends a request to\nthe Google Ad Experience Report API, by including an [API key](//cloud.google.com/docs/authentication/api-keys) with each\nrequest.\n\nAcquiring and using an API key Get a Key\n\nOr create one in the [Credentials page](https://console.cloud.google.com/apis/credentials).\n\nAfter you have an API key, your application can append the query parameter\n`key=`\u003cvar translate=\"no\"\u003eyourAPIKey\u003c/var\u003e to all request URLs.\n\nThe API key is safe for embedding in URLs; it doesn't need any encoding."]]
