Skip to main content

ListApiKeys

GET 
/v1/customers/:customer_id/api-keys

ListApiKeys returns API-key metadata.

A request that names no customer_id reads the platform-wide directory, which includes soft-deleted keys for historical spend attribution. It needs the platform admin scope or api_key_directory.read on a platform binding.

A request that names customer_id (and optionally project_id) reads only the keys of that tenant. api_key_directory.read on that customer or project authorizes it, so an org admin or a project owner can list the keys in their scope. api_keys.read does not: the read and write management keys and the Viewer hold it for the lookup RPCs. The organization-admin lift that the acting user of the Admin Console receives is never applied to this RPC.

Filter by project_id and application_keys_only to find the key that serves one application; disabling that key with UpdateApiKey stops the application.

A request that sets only page, name, project_id and application_keys_only keeps the legacy behaviour: UUID keyset pages, every status, no summary. Any other field switches to offset pages with filters, sorting and an optional summary.

Request​

Responses​

Success