> 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/databricks.md). # Databricks Allows you to configure Databricks as a destination for Inforiver writeback. When you get to the 'Add Destination' page, you have the option of using basic or OAuth authentication. If you choose basic authentication, you will need to enter the following information: * Host Name * Warehouse ID * Access Token * Catalog * Schema * Table Name

You can also use OAuth-type authentication to log in that ensures a simple and secure login process. The example below illustrates adding a Databricks destination to an existing integration using OAuth-type authentication.

OAuth type authentication for Databricks destination

#### - Fetching the hostname

#### - Fetching the warehouse ID

#### **- Generating the personal access token** **STEP 1:** Open Settings > Select Developer under user settings > Click Manage in the Access Tokens section.

**STEP 2:** Click **Generate new token**.

If required, enter the token validity.

**STEP 3:** Copy the generated token and enter it in the destination config.

#### - Fetch the catalog and schema name

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.inforiver.com/working-with-inforiver/12.-data-writeback/destinations/databricks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.