Lists the API keys owned by a project

What this operation does

Lists the API keys owned by a project.

• GETReads data · projectsapikeys.googleapis.com/v2/{parent}/keys

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Google Keys operations the program may use, and this is one of them.
3. You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.

Other Google Keys operations

• Creates a new API keyPOST · changes data
• Deletes an API key. Deleted key can be retrieved within 30 days ofDELETE · changes data
• Patches the modifiable fields of an API keyPATCH · changes data
• Undeletes an API key which was deleted within 30 daysPOST · changes data
• Find the parent project and resource name of the API keyGET · reads data
• Gets the metadata for an API keyGET · reads data
• Get the key string for an API keyGET · reads data

All 8 Google Keys operations

Questions

Can HumDay lists the api keys owned by a project in Google Keys?

Yes. This operation is published in Google Keys's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Does this change anything in my Google Keys account?

No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Google Keys.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Google Keys account.

Where this came from

Read from a published API description for Google Keys at apikeys.googleapis.com/$discovery/rest?version=v2. The description above is the provider’s own wording, not ours. Last published 2023-04-21.