Field noteOct 26, 20261 min read1 source

Deprecating the GraphQL API: timeline and migration paths

In one minute

Weaviate has deprecated its GraphQL query API as of October 26, 2026.

What changed: Weaviate announces GraphQL deprecation, with Cloud shutdown dates and migration paths; the prior only mentions GraphQL in a security-fix context.

The company says existing GraphQL users are not cut off on the announcement date, but Weaviate Cloud will end GraphQL support on May 1, 2027.

Cloud clusters with no GraphQL usage in the preceding 30 days will have it switched off on December 1, 2026. New Weaviate Cloud clusters are already created without GraphQL. Direct requests to /v1/graphql, raw GraphQL helpers, and older clients including Python v3, TypeScript v2, Java v5, and Go v5 or earlier may be affected.

Weaviate recommends current gRPC-based clients for Python, TypeScript, Java, and C#, plus Go v6. It offers @weaviate/web for gRPC-Web and a Preview REST Search API, though the latter is only a subset of GraphQL. Self-hosted users can test by setting DISABLE_GRAPHQL=true; disabled GraphQL requests return HTTP 422. The source does not set a date for complete removal from self-hosted releases or establish REST parity for every GraphQL feature.

Evidence / sources

  1. 1weaviate.io/blog/graphql-api-deprecation
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicAgent ProtocolsExplore the agent-protocols topic hub.
  2. 02topicMcpExplore the mcp topic hub.
  3. 03archiveField NotesOpen the latest editorial analysis.
  4. 04source ledgerSource LedgerInspect the public source evidence graph.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract