Deprecating the GraphQL API: timeline and migration paths

Weaviate has deprecated its GraphQL API. Existing clusters aren’t switched off immediately. Weaviate Cloud has these shutdown dates:

• New Cloud clusters already have GraphQL disabled.
• On December 1, 2026, GraphQL is switched off for clusters that haven’t used it in the last 30 days.
• On May 1, 2027, it is switched off on all remaining Cloud clusters.

Self-hosted versions released before May 1, 2027 keep GraphQL working. The first minor release after that date disables it by default, with an option to turn it back on. Removal is planned for a later release.

Check code that calls /v1/graphql or /v1/graphql/batch, uses raw GraphQL helpers or relies on older clients. The stable Go client v5 always uses GraphQL; current Python, TypeScript, Java and C# clients are most likely unaffected.

The migration guide covers client libraries and alternatives. Go v6 is a release candidate, @weaviate/web is alpha and needs v1.38.3 or later, and the REST Search API is a preview enabled by default from v1.39.7.