specification: API Commons Rate Limits specificationVersion: '0.1' schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits provider: Databricks Asset Bundles providerId: databricks-asset-bundles created: '2026-05-04' modified: '2026-09-05' generated: '2026-09-05' method: searched source: https://docs.databricks.com/aws/en/resources/limits docs: https://docs.databricks.com/aws/en/resources/limits limit_count: 14 tags: - CI/CD - Databricks - Deployment - Infrastructure as Code - Rate Limiting - Quotas - Throttling description: >- Published Databricks REST API rate limits, read from the provider's own resource-limits page (current as of 2026-09-02 per that page). This file replaces a 2026-05-04 scaffold whose free/professional/enterprise request quotas were invented — Databricks publishes no per-tier request quota. Limits are per workspace or per account, not per API key, and Declarative Automation Bundles inherit them because the CLI calls these same APIs. scope_note: >- There is no bundle-specific rate limit. `databricks bundle deploy` fans out across the Jobs, Pipelines and Workspace APIs, so the limits that bite a large bundle are the Jobs and Workspace ones below. headers: limit: null remaining: null reset: null retryAfter: null policy: null note: >- HONEST GAP. Databricks does not document any rate-limit response headers — no X-RateLimit-*, no RateLimit-*, no Retry-After — and does not state the HTTP status returned on exhaustion. A client cannot read its remaining budget from a response; it can only read the documented numbers. The prior version of this file asserted a full X-RateLimit-* header set that Databricks has never published. responseCodes: throttled: null note: The documentation does not state the status code returned when a limit is exceeded. limits: - name: DBFS API scope: workspace metric: requests_per_second limit: 30 timeFrame: second fixed: true - name: OpenSharing APIs (Providers, Recipients, Shares) scope: workspace metric: requests_per_second limit: 400 timeFrame: second - name: Jobs API — create, get, list, reset, run-now scope: workspace metric: requests_per_second limit: 20 timeFrame: second - name: Jobs API — delete, update scope: workspace metric: requests_per_second limit: 10 timeFrame: second - name: Jobs API — runs/get scope: workspace metric: requests_per_second limit: 100 timeFrame: second - name: SCIM API — account-level GET scope: account metric: requests_per_second limit: 20 timeFrame: second - name: SCIM API — workspace-level GET scope: workspace metric: requests_per_minute limit: 255 timeFrame: minute - name: Workspace API — export scope: workspace metric: requests_per_second limit: 60 timeFrame: second - name: Workspace API — import scope: workspace metric: requests_per_second limit: 30 timeFrame: second - name: Workspace API — list scope: workspace metric: requests_per_second limit: 50 timeFrame: second - name: Workspace API — delete scope: workspace metric: requests_per_second limit: 2 timeFrame: second - name: MLflow Tracking — most operations scope: workspace metric: requests_per_second limit: 120 timeFrame: second - name: MLflow Tracking — search / list scope: workspace metric: requests_per_second limit: 7 timeFrame: second - name: Secrets API scope: workspace metric: requests_per_minute limit: 1100 timeFrame: minute policies: - name: Fixed vs adjustable description: >- The limits page marks each limit as fixed (not requestable) or adjustable. Adjustable limits are raised through Databricks support, not through a plan upgrade. - name: Currency description: >- The provider states the published limits are current as of 2026-09-02. maintainers: - FN: Kin Lane email: kin@apievangelist.com