Always available

Keep a local record of enabled APIs.

The project-level Service Usage JSON API, with verified gcloud and Terraform examples.

Backed by: CloudBurrow's project registry CloudBurrow

Get started
Local scope

What it covers

The always-served Service Usage endpoint lists what the local instance actually serves. gcloud and Terraform can record changes to a project’s enabled set. A request to enable an unavailable API is refused with a reason, so a successful settings call cannot imply a service is present when it is absent.

  • List and get the APIs served by the local instance
  • Enable, disable and batch-enable APIs per project (#1352)
  • Read and manage completed operation records (#1530)
  • Verified gcloud services commands and Terraform google_project_service
Release and main

What's verified

Follow the operation matrix to see what the backend serves and the tests linked to Verified calls.

Service Usage API (v1)

10 of 10 RPCs Verified in v0.3.0

Service Usage API (v1) in v0.3.0: 10 Verified of 10
Inspect the Service Usage API (v1) operation matrix →
Local boundaries

Not supported

  • 01 / Local boundary

    Disabling an API changes its recorded state. The local API still answers calls.

  • 02 / Local boundary

    Enabling an API that this instance does not serve is refused. Folder and organization parents are outside the served scope.

Evidence source

Source: docs/compatibility.md at main 0ea2594.

Frequently asked

Questions

Will a disabled API stop answering?

No. Service Usage keeps the disabled state as project metadata. The service stays reachable for other tests.
Link to this answer
Develop locally

Build against Google Cloud APIs, locally

Free and open source under Apache-2.0. No account, no sign-up, no Google Cloud bill.

Get started