PPM site
Just another New Help App Staging Sites site
Using API Keys
*Google Sheets API can be used in Advanced Data Table.
See Advanced Data Table
When you use API keys in your applications, ensure that they are kept secure during both storage and transmission. Publicly exposing your API keys can lead to unexpected charges on your account. To help keep your API keys secure, follow these best practices:
API keys are unrestricted by default. Unrestricted keys are insecure because they can be used by anyone from anywhere. For production applications, you should set both application restrictions and API restrictions.
To add API key restrictions:
Application restrictions specify which web sites, IP addresses, or apps can use an API key. Add application restrictions based on your application type. You can only set one restriction type per API key.
Choose the restriction type based on the needs of your application.
API keys used by web applications should have HTTP restrictions. To add HTTP restrictions:
*
The following table shows example scenarios and restrictions, from most restrictive to least restrictive. We recommend using the most restrictive example that fits your use case.
https://www.example.com/path
https://www.example.com/path/path
https://www.example.com
https://sub.example.com
https://example.com
https://www.example.com/*
https://sub.example.com/*
https://example.com/*
https://*.example.com
https://*.example.com/*
API restrictions specify which APIs can be called using the API key. All API keys used by production applications should have API restrictions.
To set API restrictions:
You can create 300 API keys per project. This is a system limit, and cannot be changed using a quota increase request.
If more API keys are needed, they should be shared across multiple projects.
As the Google Sheets API is a shared service, we apply quotas and limitations to make sure it’s used fairly by all users and to protect the overall health of the Google Workspace system.
If you exceed a quota, you’ll generally receive a 429: Too many requests HTTP status code response. If this happens, you should use an exponential backoff algorithm and try again later. Provided you stay within the per-minute quotas below, there’s no limit to the number of requests you can make per day.
429: Too many requests
The following table details the request limits:
Powered by BetterDocs