Authenticate by generating a Databricks personal access token or using your configured service principal credentials.
Identify the numeric job ID of the job you want to trigger from the Databricks Jobs UI or via GET /api/2.1/jobs/list.
POST to https://YOUR_WORKSPACE.azuredatabricks.net/api/2.1/jobs/run-now with Content-Type application/json and Authorization: Bearer YOUR_TOKEN.
Set the request body to {"job_id": YOUR_JOB_ID} at minimum; optionally include jar_params, notebook_params, or python_params to override default parameters.
Capture the run_id from the response to track execution status.
Poll GET /api/2.1/jobs/runs/get?run_id=YOUR_RUN_ID until the state.life_cycle_state is TERMINATED, then check state.result_state for SUCCESS or FAILED.
Known gotchas
Use /api/2.1/jobs/run-now rather than the older /api/2.0/ path; the 2.1 API is required for multi-task job support and is the current recommended version.
Parameter override keys must exactly match what is defined in the job configuration — mismatched keys are silently ignored rather than raising an error.
The workspace hostname format differs between Azure Databricks, AWS, and GCP deployments — ensure you use the correct base URL for your cloud provider.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp