The Databricks REST API 2.0 supports services to manage your workspace, DBFS, clusters, instance pools, jobs, libraries, users and groups, tokens, and MLflow experiments and models.
This article provides an overview of how to use the REST API. Links to each API reference, authentication options, and examples are listed at the end of the article.
For information about authenticating to the REST API, see Authentication using Databricks personal access tokens. For API examples, see Examples.
The Databricks REST API supports a maximum of 30 requests/second per workspace. Requests that exceed the rate limit will receive a 429 response status code.
It can be useful to parse out parts of the JSON output. In these cases, we recommend that you to use the utility
jq. For more information, see the jq Manual. You can install
jq on MacOS using Homebrew by running
brew install jq.
STRING fields (which contain error/descriptive messaging intended to be consumed by the UI) are unstructured, and you should not depend on the format of these fields in programmatic workflows.
While most API calls require that you specify a JSON body, for
GET calls you can specify a query string.
To get the details for a cluster, run:
curl ... https://<databricks-instance>/api/2.0/clusters/get?cluster_id=<cluster-id>
To list the contents of the DBFS root, run:
curl ... https://<databricks-instance>/api/2.0/dbfs/list?path=/
Many API calls require you to specify a Databricks runtime version string. This section describes the structure of a version string in the Databricks REST API.
M- Databricks Runtime major release
F- Databricks Runtime feature release
cpu- CPU version (with
ml- Machine learning
conda- with Conda (no longer available)
scala-version- version of Scala used to compile Spark: 2.10, 2.11, or 2.12
M- Apache Spark major release
F- Apache Spark feature release
m- Apache Spark maintenance update
n- Databricks Runtime version
scala-version- version of Scala used to compile Spark: 2.10 or 2.11