---
title: "Migrate to the new APIs | Grafana Cloud documentation"
description: "Migrate to the new Grafana APIs Note New APIs are available in Grafana 12 and later. Legacy APIs are deprecated starting in Grafana 13."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# Migrate to the new Grafana APIs

> Note
> 
> New APIs are available in Grafana 12 and later. Legacy APIs are deprecated starting 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](/docs/grafana-cloud/learn-and-build/developer-resources/api-reference/http-api/apis/) 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.

## Deprecation notes

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. For details, refer to [List of available HTTP APIs](/docs/grafana-cloud/learn-and-build/developer-resources/api-reference/http-api/#list-of-available-http-apis) table.

### Query history API

The [Query History API](/docs/grafana-cloud/learn-and-build/developer-resources/api-reference/http-api/api-legacy/query_history/) 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.