# Databricks HTTP Request

> Databricks HTTP Request activity in the Databricks connector.

## Description

Performs HTTP requests to the Databricks workspace REST API by using the existing connector and connection configuration. Use it to reach Databricks endpoints that the predefined activities do not cover.

## Project compatibility

Windows | Cross-platform

## Configuration

* **Connection** - The connection established in Integration Service. Access the dropdown menu to choose, add, or manage connections.
* **Method** - The HTTP verb to use: `GET`, `POST`, `PUT`, `PATCH`, or `DELETE`.
* **Base URL** - The workspace base URL. This is read-only and provided by the connection.
* **Endpoint** - The request path, appended to the base URL. For example, `/api/2.1/jobs/list`.
* **Headers** - Request headers.
* **Query Parameters** - Request query parameters.
* **Body** - The request body, for methods that accept one.

:::note
This activity only accepts `application/json` as the content type, and does not support file upload or download. To move files in and out of a Unity Catalog volume, use [Upload a File](https://docs.uipath.com/activities/other/latest/integration-service/uipath-databricks-http-upload-file) and [Download a File](https://docs.uipath.com/activities/other/latest/integration-service/uipath-databricks-http-download-file) instead.
:::

### Output

* **Response status code** - Automatically generated output variable.
* **Response headers** - Automatically generated output variable.
* **Response body** - Automatically generated output variable.

:::note
You might see variations in the output depending on where you run the activity. In API workflows and Maestro Flow, a single response object containing all the fields is returned. In RPA workflows, not all fields are exposed, but you can still retrieve them from the exposed response object.
:::