> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/working-with-inforiver/12.-data-writeback/destinations/bigquery.md). # BigQuery Allows you to configure BigQuery as a destination for Inforiver writeback. You can either configure using the JSON or the P12 key type. The details listed in the table below will have to be entered depending on the chosen key type: | JSON(Recommended) | P12 | | ----------------- | --------------------- | | Dataset ID | Project ID | | Json Key | Dataset ID | | Table Name | Service Account Email | | | Private Key | | | Table Name | {% hint style="info" %} * If the tenant administrator creates a connection at admin level, the Dataset ID and Project ID fields will be populated automatically. * Ensure that the user has permission to SELECT, INSERT, UPDATE, and DELETE data from the table {% endhint %}

### 1. Generating the JSON key Select the **Create new key** option from the ADD KEY dropdown.

Select the JSON radio button.

### 2. Roles Ensure that the account has “Data Editor” permission.

Account should have Data Editor permissions

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.inforiver.com/working-with-inforiver/12.-data-writeback/destinations/bigquery.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.