# Deprecating the GraphQL API: timeline and migration paths

By Steven Van · 2026-10-26

GraphQL stays on until May 1, 2027 on Weaviate Cloud, but clusters unused for 30 days are switched off on December 1, 2026.

Weaviate has deprecated its GraphQL API, with nothing changing on [the day of the](<https://weaviate.io/blog/graphql-api-deprecation>)announcement. Existing clusters keep working, and the dates below set when GraphQL is switched off.

 Wait, that markup is malformed. Corrected output:

[Weaviate](<https://creatorstoolbox.com/tools/weaviate>) has deprecated its GraphQL API as of October 26, 2026, and [the migration guide](<https://docs-graphql-deprecation--docs-weaviate-io.netlify.app/weaviate/api/graphql/migration>) explains how to move. Nothing breaks on that day, and existing clusters keep working.

## Timeline on Weaviate Cloud

- New Weaviate Cloud clusters are already created with GraphQL disabled.

- On **December 1, 2026**, GraphQL is switched off for clusters that have not used it in the last 30 days.

- On **May 1, 2027**, the end-of-life date for GraphQL on Weaviate Cloud, it is switched off on all remaining clusters.

Weaviate is emailing all Weaviate Cloud customers so they know whether their clusters are affected. Cloud customers who need help can contact support through the support portal or at support@weaviate.io.

## Self-hosted Weaviate

Every version released before May 1, 2027 keeps a working GraphQL API. The first minor release after that date disables it by default, and it can be switched back on. It is removed in a later release, with no date set yet.

## Who needs to migrate

Applications that search through a current Python, TypeScript, Java or C# client are most likely not affected. Code is affected if it calls /v1/graphql or /v1/graphql/batch directly, uses a raw GraphQL helper, or uses an older client generation that builds queries as GraphQL. The current stable Go client (v5) always uses GraphQL.

## Migration paths

- **Client libraries:** the recommended path for server or container apps. Python, JavaScript/TypeScript, Java and C# are generally available. Go client v6 is a release candidate.

- **TypeScript client for web:** @weaviate/web for browsers and edge runtimes such as Cloudflare Workers or Vercel. It is an alpha release and needs Weaviate v1.38.3 or later.

- **REST Search API:** plain-HTTP JSON endpoints for stacks with no client library, such as no-code or BI tools, PHP or Ruby. It is a preview feature, enabled by default from v1.39.7, and covers Get and Aggregate queries through six endpoints.

To test, set DISABLE\_GRAPHQL to true on a non-production self-hosted instance. A disabled endpoint returns HTTP 422 with the message "graphql api is disabled".

![Weaviate](<https://www.google.com/s2/favicons?domain=weaviate.io&sz=128>)

Weaviate

Bring AI-native applications to life with less hallucination, data leakage, and vendor lock-in

[View Weaviate →](<https://creatorstoolbox.com/tools/weaviate>)

[Original source](<https://weaviate.io/blog/graphql-api-deprecation>)

[Read Deprecating the GraphQL API: timeline and migration paths on Creators Toolbox](<https://creatorstoolbox.com/blog/weaviate-deprecating-the-graphql-api-timeline-and-migration-paths>)

---
Canonical source: https://creatorstoolbox.com/blog/weaviate-deprecating-the-graphql-api-timeline-and-migration-paths