# BigQuery MCP connector

The BigQuery connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent run queries, browse datasets and check jobs in BigQuery as the signed-in person, with every call written to an audit log.

Source: https://elaichi.ai/connectors/bigquery/

## Facts

| | |
| --- | --- |
| Application | BigQuery |
| Category | Database |
| AI tools | 47 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | Yes |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once BigQuery is connected

- Run last month's revenue by region query and summarize the results
- Which BigQuery jobs are still running right now?
- List the datasets in the marketing project

## Connect BigQuery in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick BigQuery.
2. Optionally set Share with, then press Connect.
3. Supply your own BigQuery app, then approve. BigQuery needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which BigQuery tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## BigQuery MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## BigQuery MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## BigQuery MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## BigQuery MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## BigQuery MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect BigQuery to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a BigQuery tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with BigQuery through Elaichi

### Answer a data question without writing SQL

Analytics. Ask for last quarter's orders by region in plain words, let the agent run the query in BigQuery, and read the result back in the same chat.

### Pull month-end numbers from the warehouse

Finance. Run the revenue query against the finance dataset, get the result, and have it summarized for the close meeting without waiting on an analyst.

### Check campaign results in a dataset

Marketing. List the datasets in the marketing project, run a query on last week's campaign table, and get the numbers before the standup.

### Find out why a job is still running

Data engineering. List the jobs in a project, open the one that has been running for an hour, and cancel it if it is stuck.

### See who can run a routine

Security. Look up the access policy on a routine, check whether a given account has permission, and tidy up policies that have drifted.

### Set up a dataset for a new project

Operations. Create a dataset, give it a description, and later update or restore it, all without opening the BigQuery console.

## Elaichi vs Zapier MCP vs Composio for BigQuery

All three can connect BigQuery to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over BigQuery tools | Allow or restrict single BigQuery tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per BigQuery call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect BigQuery to Claude?

Connect BigQuery in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. BigQuery is one of the applications where you register an OAuth application in your own Google Cloud project once and paste its client ID and secret into Elaichi; after that, nobody else on the team needs them. Each person then sees the normal Google sign-in screen and approves access to BigQuery as themselves.

### Does BigQuery work with ChatGPT and Cursor as well as Claude?

Yes. Once BigQuery is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect BigQuery once and every client picks it up.

### What can an AI agent actually do with my BigQuery data?

An agent can run a query in BigQuery and read the result back to you, list your projects and datasets, create or update a dataset, and check on jobs, including cancelling one that is stuck. It can also list the models in a project and look up who has permission to use a routine. Short, concrete asks such as 'run the churn query for March' work better than long paragraphs.

### Does connecting BigQuery give the AI every dataset in my project?

No. Every call to BigQuery runs as the person who signed in, so an agent can only see the projects, datasets and jobs that person already has access to in BigQuery. Elaichi can narrow that further with roles and restrictions, but it never widens it.

### Can my team share one BigQuery connection?

Yes. One person connects BigQuery in Elaichi and shares the connection with a team, and nobody else ever handles the client ID or secret. Each person still signs in to Google as themselves, so the audit log names who ran which query in BigQuery.

### Can I stop an agent from deleting or changing things in BigQuery?

Yes. Restrictions in Elaichi work per action, so you can restrict deleting a BigQuery dataset, deleting a routine or cancelling a job for a role or for one person, while leaving queries open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a BigQuery connection when someone leaves?

Offboarding a person in Elaichi ends their access to BigQuery through every client at once. A shared BigQuery connection keeps working for everyone else on the team. If you disconnect BigQuery in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.

### Does the BigQuery MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. BigQuery is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for BigQuery?

Yes. Both let Claude, ChatGPT or Cursor use BigQuery. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every BigQuery call.

### How is Elaichi different from Composio for BigQuery?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to BigQuery: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 47 BigQuery tools

Every tool below is callable through https://api.elaichi.ai/mcp once BigQuery is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Get single BigQuery dataset by ID** (Get). Returns the dataset specified by datasetID. # IAM Permissions Requires the `bigquery.datasets.get` permission on the dataset. The id is the dataset ID. [GET projects/{projectsId}/datasets/{datasetsId}]
- **Delete a BigQuery dataset by ID** (Delete). Deletes the dataset specified by the datasetId value. Before you can delete a dataset, you must delete all its tables, either manually or by specifying deleteContents. Immediately after deletion, you can create another dataset with the same name. # IAM Permissions Requires the `bigquery.datasets.delete` permission on the dataset. The id is the dataset ID. [DELETE projects/{projectsId}/datasets/{datasetsId}]
- **List all BigQuery datasets** (List). Lists all datasets in the specified project to which the user has been granted the READER dataset role. # IAM Permissions Requires no specific IAM permission(s) to use this method. Results are filtered to only include datasets on which the caller has the `bigquery.datasets.get` permission. [GET projects/{projectsId}/datasets]
- **BigQuery datasets restore** (Restore). Undeletes a dataset which is within time travel window based on datasetId. If a time is specified, the dataset version deleted at that time is undeleted, else the last live version is undeleted. # IAM Permissions Requires the following IAM permission(s) to use this method: - `bigquery.datasets.create` on the project. - `bigquery.datasets.get` on the dataset. Restores a dataset deleted within the time-travel window (body: deletionTime optional). A restored dataset cannot be deleted again for 7 days (undelete cool-down). [POST projects/{projectsId}/datasets/{datasetsId}:undelete]
- **Create a BigQuery dataset** (Create). Creates a new empty dataset. # IAM Permissions Requires the `bigquery.datasets.create` permission on the project. [POST projects/{projectsId}/datasets]
- **Update a BigQuery dataset by ID** (Update). Updates information in an existing dataset. The update method replaces the entire dataset resource, whereas the patch method only replaces fields that are provided in the submitted dataset resource. # IAM Permissions Requires the `bigquery.datasets.update` permission on the dataset. The id is the dataset ID. PUT replaces the whole dataset resource: send datasetReference and every field to keep. In a BigQuery sandbox project also send defaultTableExpirationMs (max 60 days) or the call fails with billingNotEnabled. Use datasets.partial_update to change only some fields. [PUT projects/{projectsId}/datasets/{datasetsId}]
- **BigQuery datasets partial update** (Update). Updates information in an existing dataset. The update method replaces the entire dataset resource, whereas the patch method only replaces fields that are provided in the submitted dataset resource. This method supports RFC5789 patch semantics. # IAM Permissions Requires the following IAM permission(s) to use this method: - `bigquery.datasets.update` on the dataset. - `bigquery.datasets.get` on the dataset. Pass the dataset ID as dataset_id. Only the fields sent are changed. [PATCH projects/{projectsId}/datasets/{datasetsId}]
- **Get single BigQuery job by ID** (Get). Returns information about a specific job. Job information is available for a six month period after creation. Requires that you're the person who ran the job, or have the Is Owner project role. # IAM Permissions Requires the `bigquery.jobs.get` permission on the job resource. If the user matches the creator of the job, the `bigquery.jobs.create` permission on the project is required instead. The id is the job ID. [GET projects/{projectsId}/jobs/{jobsId}]
- **Create a BigQuery job** (Create). Starts a new asynchronous job. This API has two different kinds of endpoint URIs, as this method supports a variety of use cases. * The *Metadata* URI is used for most interactions, as it accepts the job configuration directly. * The *Upload* URI is ONLY for the case when you're sending both a load job configuration and a data stream together. In this case, the Upload URI accepts the job configuration and the data as two distinct multipart MIME parts. Send the job as JSON (configuration.query / load / extract / copy). Loading a local file by media upload is not supported here; load from Cloud Storage URIs instead. [POST projects/{projectsId}/jobs]
- **List all BigQuery jobs** (List). Lists all jobs that you started in the specified project. Job information is available for a six month period after creation. The job list is sorted in reverse chronological order, by job creation time. Requires the Can View project role, or the Is Owner project role if you set the allUsers property. # IAM Permissions Requires no specific IAM permission(s) to use this method. Users are able to list the jobs they created. [GET projects/{projectsId}/jobs]
- **BigQuery jobs cancel** (Cancel). Requests that a job be cancelled. This call will return immediately, and the client will need to poll for the job status to see if the cancel completed successfully. Cancelled jobs may still incur costs. # IAM Permissions Requires the `bigquery.jobs.update` permission on the job resource. If the user matches the creator of the job, the `bigquery.jobs.create` permission on the project is required instead. [POST projects/{projectsId}/jobs/{jobsId}/cancel]
- **Delete a BigQuery job by ID** (Delete). Requests the deletion of the metadata of a job. This call returns when the job's metadata is deleted. # IAM Permissions Requires the `bigquery.jobs.delete` permission on the job resource. The id is the job ID. [DELETE projects/{projectsId}/jobs/{jobsId}/delete]
- **Delete a BigQuery model by ID** (Delete). Deletes the model specified by modelId from the dataset. # IAM Permissions Requires the `bigquery.models.delete` permission on the model. The id is the model ID. [DELETE projects/{projectsId}/datasets/{datasetsId}/models/{modelsId}]
- **Update a BigQuery model by ID** (Update). Patch specific fields in the specified model. # IAM Permissions Requires the `bigquery.models.updateMetadata` permission on the model. The id is the model ID. [PATCH projects/{projectsId}/datasets/{datasetsId}/models/{modelsId}]
- **List all BigQuery models** (List). Lists all models in the specified dataset. Requires the READER dataset role. After retrieving the list of models, you can get information about a particular model by calling the models.get method. # IAM Permissions Requires the `bigquery.models.list` permission on the dataset. [GET projects/{projectsId}/datasets/{datasetsId}/models]
- **Get single BigQuery model by ID** (Get). Gets the specified model resource by model ID. # IAM Permissions Requires the `bigquery.models.getMetadata` permission on the model. The id is the model ID. [GET projects/{projectsId}/datasets/{datasetsId}/models/{modelsId}]
- **BigQuery project service accounts lookup** (Action). RPC to get the service account for a project used for interactions with Google Cloud KMS. Requires the `bigquery.jobs.create` permission on the project resource. This permission is required to authorize the retrieval of the project's service identity for technical management tasks like encryption configuration. [GET projects/{projectsId}/serviceAccount]
- **List all BigQuery projects** (List). RPC to list projects to which the user has been granted any project role. Users of this method are encouraged to consider the Resource Manager API, which provides the underlying data for this method and has more capabilities. # IAM Permissions Requires no specific IAM permission(s) to use this method. The results are filtered to only include projects on which the caller has been granted a project-level role such as a BigQuery predefined IAM role or a basic role such as Viewer or Owner. [GET projects]
- **Create a BigQuery query** (Create). Runs a BigQuery SQL query synchronously and returns query results if the query completes within a specified timeout. # IAM Permissions Requires the `bigquery.jobs.create` permission on the project resource. Data-level permissions are highly dependent on the SQL statement being executed. While standard queries require data access (such as `bigquery.tables.getData`), complex operations like DDL or DCL may require permissions to manage reservations, IAM policies, or project settings. Runs a query and waits up to timeoutMs for results; if jobComplete is false, poll query_results.get with the returned jobReference.jobId (and location). DML (INSERT/UPDATE/DELETE/MERGE) needs a project with billing; sandbox projects allow SELECT and DDL only. [POST projects/{projectsId}/queries]
- **Get single BigQuery query result by ID** (Get). RPC to get the results of a query job. # IAM Permissions Requires the following IAM permission(s) to use this method: - `bigquery.jobs.get` on the job. - `bigquery.tables.getData` on the destination table. If the user matches the creator of the job, the following IAM permission(s) are required instead: - `bigquery.jobs.create` on the project. - `bigquery.tables.getData` on the destination table. The id is the job ID returned by queries.create (jobReference.jobId) or jobs.create. [GET projects/{projectsId}/queries/{queriesId}]
- **BigQuery routine iam permissions verify** (Verify). Returns permissions that a caller has on the specified resource. If the resource does not exist, this will return an empty set of permissions, not a `NOT_FOUND` error. Note: This operation is designed to be used for building permission-aware UIs and command-line tools, not for authorization checking. This operation may "fail open" without warning. [POST projects/{projectsId}/datasets/{datasetsId}/routines/{routinesId}:testIamPermissions]
- **BigQuery routine iam policies lookup** (Action). Gets the access control policy for a resource. Returns an empty policy if the resource exists and does not have a policy set. [POST projects/{projectsId}/datasets/{datasetsId}/routines/{routinesId}:getIamPolicy]
- **BigQuery routine iam policies bulk update** (Update). Sets the access control policy on the specified resource. Replaces any existing policy. Can return `NOT_FOUND`, `INVALID_ARGUMENT`, and `PERMISSION_DENIED` errors. [POST projects/{projectsId}/datasets/{datasetsId}/routines/{routinesId}:setIamPolicy]
- **Delete a BigQuery routine by ID** (Delete). Deletes the routine specified by routineId from the dataset. # IAM Permissions Requires the `bigquery.routines.delete` permission on the routine. The id is the routine ID. [DELETE projects/{projectsId}/datasets/{datasetsId}/routines/{routinesId}]
- **List all BigQuery routines** (List). Lists all routines in the specified dataset. Requires the READER dataset role. # IAM Permissions Requires the `bigquery.routines.list` permission on the dataset. [GET projects/{projectsId}/datasets/{datasetsId}/routines]
- **Get single BigQuery routine by ID** (Get). Gets the specified routine resource by routine ID. # IAM Permissions Requires the `bigquery.routines.get` permission on the routine. The id is the routine ID. [GET projects/{projectsId}/datasets/{datasetsId}/routines/{routinesId}]
- **Update a BigQuery routine by ID** (Update). Updates information in an existing routine. The update method replaces the entire Routine resource. # IAM Permissions Requires the `bigquery.routines.update` permission on the routine. The id is the routine ID. [PUT projects/{projectsId}/datasets/{datasetsId}/routines/{routinesId}]
- **Create a BigQuery routine** (Create). Creates a new routine in the dataset. # IAM Permissions Requires the `bigquery.routines.create` permission on the dataset. [POST projects/{projectsId}/datasets/{datasetsId}/routines]
- **Get single BigQuery row access policy by ID** (Get). Gets the specified row access policy by policy ID. # IAM Permissions Requires the `bigquery.rowAccessPolicies.get` permission on the table. The id is the row access policy ID. [GET projects/{projectsId}/datasets/{datasetsId}/tables/{tablesId}/rowAccessPolicies/{rowAccessPoliciesId}]
- **Delete a BigQuery row access policy by ID** (Delete). Deletes a row access policy. # IAM Permissions Requires the following IAM permission(s) on the table: - `bigquery.rowAccessPolicies.delete` - `bigquery.rowAccessPolicies.setIamPolicy`. The id is the row access policy ID. Deleting the last row access policy on a table needs force=true (otherwise BigQuery refuses, because the table would become readable by everyone with table access). [DELETE projects/{projectsId}/datasets/{datasetsId}/tables/{tablesId}/rowAccessPolicies/{rowAccessPoliciesId}]
- **List all BigQuery row access policies** (List). Lists all row access policies on the specified table. # IAM Permissions Requires the `bigquery.rowAccessPolicies.list` permission on the table. [GET projects/{projectsId}/datasets/{datasetsId}/tables/{tablesId}/rowAccessPolicies]
- **BigQuery row access policies bulk delete** (Delete). Deletes provided row access policies. # IAM Permissions Requires the following IAM permission(s) on the table: - `bigquery.rowAccessPolicies.delete` - `bigquery.rowAccessPolicies.setIamPolicy`. [POST projects/{projectsId}/datasets/{datasetsId}/tables/{tablesId}/rowAccessPolicies:batchDelete]
- **Update a BigQuery row access policy by ID** (Update). Updates a row access policy. # IAM Permissions Requires the following IAM permission(s) on the table: - `bigquery.rowAccessPolicies.update` - `bigquery.rowAccessPolicies.setIamPolicy` - `bigquery.tables.getData`. The id is the row access policy ID. [PUT projects/{projectsId}/datasets/{datasetsId}/tables/{tablesId}/rowAccessPolicies/{rowAccessPoliciesId}]
- **Create a BigQuery row access policy** (Create). Creates a row access policy. # IAM Permissions Requires the following IAM permission(s) on the table: - `bigquery.rowAccessPolicies.create` - `bigquery.rowAccessPolicies.setIamPolicy` - `bigquery.tables.getData`. [POST projects/{projectsId}/datasets/{datasetsId}/tables/{tablesId}/rowAccessPolicies]
- **BigQuery row access policy iam permissions verify** (Verify). Returns permissions that a caller has on the specified resource. If the resource does not exist, this will return an empty set of permissions, not a `NOT_FOUND` error. Note: This operation is designed to be used for building permission-aware UIs and command-line tools, not for authorization checking. This operation may "fail open" without warning. [POST projects/{projectsId}/datasets/{datasetsId}/tables/{tablesId}/rowAccessPolicies/{rowAccessPoliciesId}:testIamPermissions]
- **BigQuery row access policy iam policies lookup** (Action). Gets the access control policy for a resource. Returns an empty policy if the resource exists and does not have a policy set. [POST projects/{projectsId}/datasets/{datasetsId}/tables/{tablesId}/rowAccessPolicies/{rowAccessPoliciesId}:getIamPolicy]
- **BigQuery table iam permissions verify** (Verify). Returns permissions that a caller has on the specified resource. If the resource does not exist, this will return an empty set of permissions, not a `NOT_FOUND` error. Note: This operation is designed to be used for building permission-aware UIs and command-line tools, not for authorization checking. This operation may "fail open" without warning. [POST projects/{projectsId}/datasets/{datasetsId}/tables/{tablesId}:testIamPermissions]
- **BigQuery table iam policies bulk update** (Update). Sets the access control policy on the specified resource. Replaces any existing policy. Can return `NOT_FOUND`, `INVALID_ARGUMENT`, and `PERMISSION_DENIED` errors. [POST projects/{projectsId}/datasets/{datasetsId}/tables/{tablesId}:setIamPolicy]
- **BigQuery table iam policies lookup** (Action). Gets the access control policy for a resource. Returns an empty policy if the resource exists and does not have a policy set. [POST projects/{projectsId}/datasets/{datasetsId}/tables/{tablesId}:getIamPolicy]
- **BigQuery table rows bulk create** (Create). Streams data into BigQuery one record at a time without needing to run a load job. # IAM Permissions Requires the following IAM permission(s) to use this method: - `bigquery.tables.updateData` on the table. - `bigquery.tables.get` on the table. - `bigquery.datasets.get` on the dataset. Streams rows into the table: rows = [{json: {column: value}, insertId?}]. Billed streaming insert: projects without billing (BigQuery sandbox / free tier) get accessDenied "Streaming insert is not allowed in the free tier"; write with a query job (jobs.create with destinationTable) instead. [POST projects/{projectsId}/datasets/{datasetsId}/tables/{tablesId}/insertAll]
- **List all BigQuery table rows** (List). List the content of a table in rows. # IAM Permissions Requires the `bigquery.tables.getData` permission on the table. Rows come back as {f: [{v: value}]} in the order of the table schema (use tables.get for the column names). [GET projects/{projectsId}/datasets/{datasetsId}/tables/{tablesId}/data]
- **List all BigQuery tables** (List). Lists all tables in the specified dataset. Requires the READER dataset role. # IAM Permissions Requires the `bigquery.tables.list` permission on the dataset. [GET projects/{projectsId}/datasets/{datasetsId}/tables]
- **Create a BigQuery table** (Create). Creates a new, empty table in the dataset. # IAM Permissions Requires the `bigquery.tables.create` permission on the dataset. [POST projects/{projectsId}/datasets/{datasetsId}/tables]
- **Update a BigQuery table by ID** (Update). Updates information in an existing table. The update method replaces the entire Table resource, whereas the patch method only replaces fields that are provided in the submitted Table resource. # IAM Permissions Requires the `bigquery.tables.update` permission on the table. The id is the table ID. PUT replaces the whole table resource: send tableReference, schema and every field to keep. In a BigQuery sandbox project also send expirationTime (within 60 days) or the call fails with billingNotEnabled. Use tables.partial_update to change only some fields. [PUT projects/{projectsId}/datasets/{datasetsId}/tables/{tablesId}]
- **Delete a BigQuery table by ID** (Delete). Deletes the table specified by tableId from the dataset. If the table contains data, all the data will be deleted. # IAM Permissions Requires the `bigquery.tables.delete` permission on the table. The id is the table ID. [DELETE projects/{projectsId}/datasets/{datasetsId}/tables/{tablesId}]
- **Get single BigQuery table by ID** (Get). Gets the specified table resource by table ID. This method does not return the data in the table, it only returns the table resource, which describes the structure of this table. # IAM Permissions Requires the `bigquery.tables.get` permission on the table. The id is the table ID. [GET projects/{projectsId}/datasets/{datasetsId}/tables/{tablesId}]
- **BigQuery tables partial update** (Update). Updates information in an existing table. The update method replaces the entire table resource, whereas the patch method only replaces fields that are provided in the submitted table resource. This method supports RFC5789 patch semantics. # IAM Permissions Requires the following IAM permission(s) on the table: - `bigquery.tables.update` - `bigquery.tables.get`. Pass the table ID as table_id. Only the fields sent are changed. [PATCH projects/{projectsId}/datasets/{datasetsId}/tables/{tablesId}]
