Manage Kibana dashboards as code: Commit to Git, promote across environments, and automate deployments with the Kibana API and Terraform. The Kibana Dashboards and Visualizations APIs are production-ready in Elastic 9. 5, available across all subscription tiers, with full backward compatibility. Define your dashboards as JSON, commit them to Git, and then deploy across environments using continuous integration and continuous deployment (CI/CD) pipelines, Terraform , or whatever tooling you already have. Over 50 teams tested the API during technical preview in 9. 4 , some already running it in production.
5 also adds new endpoints (in technical preview) for Tags , with Markdown and Links panel endpoints available now in Elastic Cloud Serverless and landing in 9. During technical preview, the API shape could change between releases. [1] That's no longer the case. General availability (GA) means: Complete backward compatibility. New fields and panel types will be added over time, but existing fields and behavior remain unchanged. Any future breaking changes would be very carefully considered and would only be introduced in a new major stack version. Production-ready with full support.
The API carries Elastic's full support guarantees. You can safely use it in production environments for automated deployments, environment promotion, and programmatic dashboard management. 5 also introduces a new standalone endpoint for Tags , which let you categorize and filter dashboards. Now you can manage them programmatically through dedicated CRUD endpoints, making it easier to organize dashboards at scale across environments. New Markdown and Links panel endpoints are available now in Serverless and will land in the next stack release (9. The Dashboards API supports all by-value panels in 9.
5 (those defined directly in a dashboard, as opposed to library panels saved for reuse). Every supported panel type has a typed, validated schema. The Dashboards API enables a full dashboards-as-code workflow: Export a dashboard as clean, diffable JSON, commit it to Git as the source of truth, review changes in pull requests, and deploy the same definition across development, staging, and production. Once a dashboard is managed as code, treat Git as the single source of truth: Changes made directly in the UI are overwritten the next time you deploy.