docs/sources/developer-resources/api-reference/http-api/apis-migration.md
{{< admonition type="note" >}} New APIs are available in Grafana 12 and later. Legacy APIs are deprecated starting in Grafana 13. {{< /admonition >}}
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.
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. Refer to the table for details:
| Feature | New API | Legacy API |
|---|---|---|
| Dashboards | /apis/dashboard.grafana.app/* | /api/dashboards/* |
| Folders | /apis/folder.grafana.app/* | /api/folders/* |
| Playlists | /apis/playlist.grafana.app/* | Not available |
| Resource history | /apis/<group>/<version>/namespaces/* | Not available |
| Secrets management | /apis/secret.grafana.app/* | Not available |
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.