Source: weaviate.io/blog/graphql-api-deprecation
GraphQL was Weaviate's first query API. The company says it is moving to one query API built on gRPC, with REST Search API endpoints for stacks that cannot run a client. Typed gRPC messages return errors as status codes, and metadata is a field on the result rather than a separate block.
Clusters that have not used GraphQL in the last 30 days will have it switched off on December 1, 2026. Every other Weaviate Cloud cluster loses it on May 1, 2027, which is also the end-of-life date for GraphQL on Weaviate Cloud. Self-hosted users can set DISABLE_GRAPHQL to true today to test their applications, and disabled endpoints return HTTP 422.
Developers who use the current Python, TypeScript, Java or C# clients are most likely unaffected. Go users on the stable v5 client still query over GraphQL, and the v6 client, which uses gRPC, is a release candidate. Weaviate says the first minor release after May 1, 2027 disables GraphQL by default, and the code is removed in a later release with no date set yet.
Why it matters if you build agents
If your code, proxies or no-code tools send raw GraphQL to /v1/graphql, plan a move to a client library, the TypeScript web client or the REST Search API before the December 1, 2026 and May 1, 2027 dates. Search your code for /v1/graphql and raw GraphQL helpers to find your calls.
Some GraphQL-only features have no equivalent yet, so check the migration guide before you start. Weaviate says it will add missing capabilities if customers ask for them.
Get stories like this every weekday
One short email with the day's agent tooling news.