REST API V1.2

The Databricks REST API allows you to programmatically access Databricks instead of going through our Web UI.

This document covers REST API 1.2. For most use cases, we recommend using the REST API V2.0. It supports most of the functionality of the 1.2 API, as well as additional functionalities. You may still find the 1.2 API useful if you are using the execution context and command execution APIs.

REST API Use Cases

  • Create a hook in Jenkins to replace an old version of your library jar with the latest version.
  • Start Spark jobs triggered from your existing production systems or from systems like Airflow and Luigi.
  • Programmatically bring up a cluster of a certain size at a fixed time of day and then shut it down at night.
  • and more...

Terminology

  • Execution contexts: creating unique variable namespaces where Spark commands can be called
  • Command execution: executing commands within a specific execution context

Details

  • This REST API runs over HTTPS.
  • For retrieving information, HTTP GET is used.
  • For state modification, HTTP POST is used.
  • For file upload, multipart/form-data is used.
  • Otherwise application/x-www-form-urlencoded is used.
  • The response content type is json.
  • Starting from version 1.1, basic authentication is used to authenticate the user for every API call.
  • User’s credentials are base64 encoded and are in the HTTP header for every API call.
  • for example “Authorization: Basic YWRtaW46YWRtaW4=”.

Getting Started

In the following examples, replace YOUR_DOMAIN with the <REGION>.azuredatabricks.net domain name of your Databricks deployment.

Test Your Connection

> telnet YOUR_DOMAIN 443

Trying 52.11.163.202...
Connected to YOUR_DOMAIN.
Escape character is '^]'.

> nc -v -z YOUR_DOMAIN 443
found 1 connections:
     1: flags=82<CONNECTED,PREFERRED>
    outif utun0
    src x.x.x.x port 59063
    dst y.y.y.y port 443
    rank info not available
    TCP aux info available

Connection to YOUR_DOMAIN port 443 [TCP/HTTPS] succeeded!

You can use either tool above to test the connection. Port 443 is default HTTPS port and users can run the REST API on this port.

curl -n https://YOUR_DOMAIN/api/1.2/clusters/list

If you cannot connect to port 443 please reach out to support@databricks.com with your account URL.

Sample REST API calls

We cover some sample curl commands below, but you can also use an HTTP library in your programming language of choice.

GET request

curl -n https://YOUR_DOMAIN/api/1.2/clusters/list

Note: If your URL has the “&” character in it when you have more than one command, you’ll need to quote that URL so UNIX won’t interpret that as a command separator: .. code:

curl -n 'https://YOUR_DOMAIN/api/1.2/commands/status?clusterId=batVenom&contextId=35585555555555&commandId=45382422555555555'

POST Request with application/x-www-form-urlencoded

curl -X POST -n https://YOUR_DOMAIN/api/1.2/contexts/create \
  -d "language=scala&clusterId=batVenom"

List of API calls

Execution Context

  • https://YOUR_DOMAIN/api/1.2/contexts/create – creates an execution context on a specified cluster for a given programming language
    • POST Request with application/x-www-form-urlencoded:
      • data = {“language”: “scala”, “clusterId”: “peaceJam”}
  • https://YOUR_DOMAIN/api/1.2/contexts/status – shows the status of an existing execution context
    • GET request:
      • Example arguments: clusterId=peaceJam&contextId=179365396413324
      • Status is one of [“Pending”, “Running”, “Error”]
  • https://YOUR_DOMAIN/api/1.2/contexts/destroy – destroys an execution context
    • POST Request with application/x-www-form-urlencoded:
      • data = {“contextId” : “1793653964133248955”, “clusterId” : “peaceJam”}

Command Execution

Known limitations: command execution does not support %run.

  • https://YOUR_DOMAIN/api/1.2/commands/execute – runs a given command or file.
    • POST Request with application/x-www-form-urlencoded:
      • data = {“language”: “scala”, “clusterId”: “peaceJam”, “contextId” : “5456852751451433082”, “command”: “sc.parallelize(1 to 10).collect”}
    • POST Request with multipart/form-data:
      • data = {“language”: “python”, “clusterId”: “peaceJam”, “contextId” : “5456852751451433082”}
      • files = {“command”: ”./myfile.py”}
  • https://YOUR_DOMAIN/api/1.2/commands/status – shows one command’s status or result
    • GET Request
      • Example arguments: clusterId=peaceJam&contextId=5456852751451433082&commandId=5220029674192230006
      • status can be [“Queued”, “Running”, “Cancelling”, “Finished”, “Cancelled”, “Error”]
  • https://YOUR_DOMAIN/api/1.2/commands/cancel – cancels one command
    • POST Request with application/x-www-form-urlencoded:
      • data = {“clusterId”: “peaceJam”, “contextId” : “5456852751451433082”, “commandId” : “2245426871786618466”}

Example: Upload Spark Jar and Run in Databricks

  • Use the REST API V2.0 to upload a library and attach it to a cluster.
  • Create an execution context.
curl -X POST -n  https://YOUR_DOMAIN/api/1.2/contexts/create \
-d "language=scala&clusterId=batVenom"
{
"id": "3558513128163162828"
}
  • Execute a command that uses your jar.
curl -X POST -n https://YOUR_DOMAIN/api/1.2/commands/execute \
-d 'language=scala&clusterId=batVenom&contextId=3558513128163162828&command=println(com.databricks.apps.logs.chapter1.LogAnalyzer.processLogFile(sc,null,"dbfs:/somefile.log"))'
{
"id": "4538242203822083978"
}
  • Check on the status of your command. It may not return immediately if you are running a lengthy Spark job.
curl -n 'https://YOUR_DOMAIN/api/1.2/commands/status?clusterId=batVenom&contextId=3558513128163162828&commandId=4538242203822083978'
{
"id": "4538242203822083978",
"results": {
    "data": "Content Size Avg: 1234, Min: 1234, Max: 1234",
    "resultType": "text"
},
"status": "Finished"
}