Google BigQuery Reservation API
Browse all Google APIs✓ Official Vendor SpecAnalyticsBusiness Intelligenceoauth215 EndpointsREST
For Agents
Manage BigQuery flat-rate slot capacity, reservations, and project assignments. Agents can buy commitments, split slots between teams, and reassign reservations during failover.
Use for: I need to buy 500 BigQuery slots in the US region for a year, List all reservations in a project and location, Assign reservation prod-analytics to project myproj for QUERY jobs, Find which reservation a given project is currently assigned to
Not supported: Does not run queries, transfer data, or manage column-level policies — use for slot capacity, reservation, and assignment management only.
The BigQuery Reservation API manages flat-rate compute capacity for BigQuery: capacityCommitments buy slots for a term, reservations group those slots, and assignments bind reservations to projects, folders, or organisations. The API also supports failover, splitting and merging commitments, and searching assignments. Teams use this when on-demand pricing becomes volatile and they want predictable, reserved slot capacity. It does not run queries; it controls how the capacity that runs queries is allocated.
Install Jentic One Beta
Connect the BigQuery Reservation API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BigQuery Reservation API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with BigQuery Reservation API.
Purchase capacityCommitments for a region with a slot count and plan
Create reservations that hold a subset of committed slots and configure idle slot sharing
Assign reservations to projects, folders, or organisations for query routing
Split, merge, or move capacityCommitments to rebalance across regions
Trigger failover on a reservation to redirect traffic to a secondary region
Search assignments across the resource hierarchy to audit slot routing
List reservations and inspect remaining slot capacity per region
Use Cases
Patterns agents use BigQuery Reservation API for, with concrete tasks.
★ Predictable Slot Capacity
Buy capacityCommitments and group them into reservations so query workloads run on predictable, billed-by-the-hour capacity instead of on-demand pricing. Commitments are managed at /v1/{parent}/capacityCommitments and reservations at /v1/{parent}/reservations. Idle slot sharing lets unused slots flow between reservations within the same admin project.
Create a 12-month FLEX capacityCommitment for 500 slots in the US region under admin project bq-admin.
Workload Isolation
Create separate reservations for ETL, BI, and ad-hoc analyst workloads, then assign each to the correct projects so a heavy ETL job cannot starve the dashboards. Assignments are managed at /v1/{parent}/assignments with jobType (QUERY, PIPELINE, ML_EXTERNAL). This protects interactive query latency while keeping pipelines on dedicated slots.
Create reservation prod-bi with 200 slots and assign it to project bi-prod for QUERY jobs.
Capacity Rebalancing
Use split/merge on capacityCommitments and move/searchAllAssignments to rearrange slots between teams without releasing the underlying commitment. /v1/{parent}/capacityCommitments:merge and /v1/{name}:split allow capacity to follow shifting workloads. /v1/{parent}:searchAssignments shows where every reservation is currently bound.
Split capacityCommitment projects/admin/locations/US/capacityCommitments/abc into commitments of 600 and 400 slots.
DR and Failover
Failover a reservation to a secondary region using /v1/{name}:failoverReservation when the primary region is degraded. Combined with cross-region replication of datasets, this gives a path to keep BI dashboards running during outages. Slot capacity follows the failover rather than requiring fresh purchases.
Trigger failoverReservation on projects/admin/locations/us-central1/reservations/prod-analytics to its configured secondary region.
Agent-Driven Capacity Ops
An AI agent monitors slot utilisation and submits split/merge or assignment changes through Jentic when workloads shift. Operations teams describe a desired state in natural language and the agent issues the right reservation API calls. OAuth credentials never leave the Jentic vault.
From the request 'shift 100 slots from BI to ETL during nightly load', split the BI reservation, create or update the ETL reservation, and confirm new slot counts.
Key Endpoints
15 endpoints — the bigquery reservation api manages flat-rate compute capacity for bigquery: capacitycommitments buy slots for a term, reservations group those slots, and assignments bind reservations to projects, folders, or organisations.
METHOD
PATH
DESCRIPTION
POST
/v1/{+parent}/capacityCommitments
Purchase a capacity commitment in a region
POST
/v1/{+name}:split
Split a capacity commitment into two
POST
/v1/{+parent}/capacityCommitments:merge
Merge multiple commitments into one
POST
/v1/{+parent}/reservations
Create a reservation
POST
/v1/{+parent}/assignments
Assign a reservation to a project, folder, or org
POST
/v1/{+name}:failoverReservation
Failover a reservation to its secondary region
GET
/v1/{+parent}:searchAssignments
Search assignments across the hierarchy
POST
/v1/{+parent}/capacityCommitments
Purchase a capacity commitment in a region
POST
/v1/{+name}:split
Split a capacity commitment into two
POST
/v1/{+parent}/capacityCommitments:merge
Merge multiple commitments into one
POST
/v1/{+parent}/reservations
Create a reservation
POST
/v1/{+parent}/assignments
Assign a reservation to a project, folder, or org
POST
/v1/{+name}:failoverReservation
Failover a reservation to its secondary region
GET
/v1/{+parent}:searchAssignments
Search assignments across the hierarchy
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Google OAuth 2.0 client credentials and refresh tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive short-lived, scope-limited access tokens at call time and never see the refresh token.
Intent-based discovery
Agents search Jentic with intents like 'buy BigQuery slots' or 'assign a reservation' and Jentic returns the matching capacityCommitment, reservation, or assignment operation with its full schema.
Time to first call
Direct integration: 1-2 days for OAuth and the commitment/reservation/assignment data model. Through Jentic: under 30 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using BigQuery Reservation API through Jentic.
What authentication does the BigQuery Reservation API use?
The API uses Google OAuth 2.0 with the cloud-platform and bigquery scopes. Through Jentic, the OAuth refresh token is held in the encrypted vault and the agent receives only short-lived access tokens for each call.
Can I buy and split slot capacity with this API?
Yes. POST /v1/{parent}/capacityCommitments creates a commitment with a slotCount and plan (FLEX, MONTHLY, ANNUAL); POST /v1/{name}:split splits it into two; and POST /v1/{parent}/capacityCommitments:merge combines them again. Reservations and assignments handle how those slots are routed to projects.
What are the rate limits for the BigQuery Reservation API?
Project-level quotas apply: typically modest write QPS on commitments, reservations, and assignments, and bursty read QPS for list/search endpoints. Specific values are visible per project in the Google Cloud quotas page.
How do I assign a reservation to a project through Jentic?
Search Jentic for 'assign a BigQuery reservation to a project', load the schema for POST /v1/{parent}/assignments, and execute with assignee, jobType (QUERY, PIPELINE, or ML_EXTERNAL), and the reservation name. Jentic injects the OAuth token automatically.
Is the BigQuery Reservation API free?
The API has no per-call surcharge, but capacityCommitments are billed by slot count and plan duration, and reserved slots are billed even when idle. Compare flat-rate cost against on-demand bytes-scanned pricing for your workloads before purchasing.
Does this API run queries?
No. Reservations only allocate the slot capacity that BigQuery consumes when queries run. Use the BigQuery API to submit query, load, and extract jobs against that capacity.
GET STARTED