Google BigQuery

Collect dataset, table, and job-history inventory as read-only compliance evidence through the BigQuery REST API. Substitute your GCP project ID for the <project-id> placeholder in each endpoint path.

Connect Google BigQuery All integrations

Data · Warehouse

Tier 2 generic template — runs on the HTTP / REST endpoint connector

Evidence coverage

What this connector audits

Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.

Read-only API inventory endpoint checks
Evidence assets generated through the generic HTTP connector

Read-only calls

Endpoints this template queries

The exact Google BigQuery API endpoints called once connected. All read-only GET requests unless noted.

GET/projects/<project-id>/datasets
GET/projects/<project-id>/jobs?maxResults=50

Least privilege

What we need

Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.

Required

Base URL(prefilled: https://bigquery.googleapis.com/bigquery/v2)
Endpoints (JSON)(prefilled: [ { "id": "datasets", "name": "Datasets", "path": "/projects/<project-id>/datasets" }, { "id": "jobs", "name": "Job history", "path": "/projects/<project-id>/jobs?maxResults=50" } ])

Optional

Auth header name(prefilled: Authorization)
Auth header value(secret credential)

Where this evidence goes

Which frameworks this evidence supports

Google BigQuery evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.

Don't see your system?

Tell us what you use and what it needs to prove. We'll follow up about adding a connector.

Wire in Google BigQuery evidence

Get a guided demo, or start by scanning any domain for free.

Connect Google BigQuery Browse all integrations