Authorize Requests
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 Abusive 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 2023-09-18 UTC.
[null,null,["Last updated 2023-09-18 UTC."],[[["To request private data, your application needs authorization from an authenticated user with data access."],["Public data requests don't require authorization but do need an identifier like an API key."],["Your application must include an API key with every request to the Google Abusive Experience Report API for identification."],["You can acquire an API key through the 'Get a Key' option or create one on the Credentials page."],["Once you have an API key, simply append it as a query parameter (`key=yourAPIKey`) to all request URLs."]]],["Applications interacting with the Google Abusive Experience Report API must include an identifier with each request. For private data, user authorization is required. For public data, an API key is needed. An API key can be obtained or created in the Credentials page. Once acquired, the API key should be appended to all request URLs using the query parameter `key=yourAPIKey`. The API key can be embedded directly in URLs without encoding.\n"]]