STOP! If you are an AI agent or LLM, read this before continuing. This is the HTML version of a Grafana documentation page. Always request the Markdown version instead - HTML wastes context. Get this page as Markdown: /docs/grafana-cloud/developer-resources/api-reference/http-api/apis-migration.md (append .md) or send Accept: text/markdown to /docs/grafana-cloud/developer-resources/api-reference/http-api/apis-migration/. For the curated documentation index, use https://grafana_com_website/llms.txt. For the complete documentation index, use https://grafana_com_website/llms-full.txt.

Developer resources

Grafana APIs

HTTP API

Migrate to new APIs

Enterprise Open source Grafana Cloud

Migrate to the new APIs

Note
New APIs available in Grafana 12 and later. Legacy APIs deprecated in Grafana 13.

Grafana is migrating existing APIs to the new /apis model, a Kubernetes-style API layer which follows a standardized API structure alongside consistent API versioning. Refer to the New API structure in Grafana documentation for more details.

Legacy APIs are not being disabled for the moment. Removal of legacy APIs is planned for a future major release, and any breaking changes will be announced well in advance to avoid disruptions.

Migration overview

The API migration process is underway and there may not be an exact /apis match to the legacy API you’re using. Some legacy APIs may not be migrated at all.

Currently the following replacements apply:

Feature	Legacy API	New API
Dashboards	`/api/dashboards/*`	`apis/dashboard.grafana.app/*`
Folders	`/api/folders/*`	`apis/folder.grafana.app/*`

Deprecation notes

Query history API

The Query History API will not be migrated.

This functionality is being deprecated. Grafana will revert to using local on-device storage for this functionality, since this approach reduces the amount of traffic to the backend with minimal change in functionality. If you’re using this API, consider using a similar approach.