Weaviate · GraphQL deprecation
Is your code affected by the Weaviate GraphQL shutdown?
Weaviate is switching off its GraphQL API: on idle Weaviate Cloud clusters from December 1, 2026, and on all Weaviate Cloud clusters on May 1, 2027. Paste your code, lockfile or n8n workflow below, or pick a folder, to see which calls and client versions still use GraphQL.
Updated October 27, 2026.
Everything runs in your browser. Your code is not uploaded.
Which clients use GraphQL
From Weaviate's migration guide. Current clients query over gRPC, so not every Weaviate user is affected.
| Client or call | GraphQL use | Move to |
|---|---|---|
| Python weaviate-client 3.x (weaviate.Client) | Uses GraphQL for every query | Upgrade to 4.11+ and the v4 API |
| Python weaviate-client 4.0 to 4.3 | Searches through GraphQL | Upgrade to 4.11+ |
| Python weaviate-client 4.4 to 4.10 | Aggregate queries through GraphQL | Upgrade to 4.11+ |
| graphql_raw_query() in any Python version | Always GraphQL | Rewrite with collection.query / collection.aggregate |
| npm weaviate-ts-client (v2) | Uses GraphQL | weaviate-client 3.4+ on Node, @weaviate/web in browsers |
| npm weaviate-client 3.0 to 3.3 | Aggregate queries through GraphQL | Upgrade to 3.4+ |
| Java io.weaviate:client (v5 and earlier) | Uses GraphQL | io.weaviate:client6 |
| Go weaviate-go-client v5 and earlier | Uses GraphQL for every search | weaviate-go-client/v6 |
| Direct POST /v1/graphql (fetch, curl, n8n HTTP Request, BI tools) | Fails with HTTP 422 | A client library, or the REST Search API |
| C# client, Python 4.11+, npm weaviate-client 3.4+, Java client6, Go v6 | Not affected | Nothing to change |
Where to move queries
- Servers and containers: a current client library (Python, JavaScript/TypeScript on Node, Go v6, Java client6, C#). It covers every Get and Aggregate query.
- Browsers and edge runtimes such as Cloudflare Workers or Vercel:
@weaviate/web, the same client API over gRPC-Web. - No client available (no-code tools, BI, other languages): the REST Search API,
POST /v1/search/{collection}/…and/v1/aggregate/{collection}. It is in Preview and does not support groupBy, rerank, sort, generative search, multiple target vectors or aggregate statistics.
How to test before the switch-off
- Run the check above on each repository and on exported n8n, Make or Zapier workflows that call Weaviate.
- Self-hosted: start a copy of Weaviate with
DISABLE_GRAPHQL=true. Weaviate Cloud: create a new cluster, which has GraphQL off. - Point a staging copy of the app at it and compare search results with production for the same queries, filters included.
- Watch logs for HTTP 422 "graphql api is disabled". Idle Cloud clusters lose GraphQL on December 1, 2026, so a cluster used only by a monthly job is worth checking early.
Questions
When does Weaviate switch off GraphQL?
Weaviate announced the deprecation on October 26, 2026. On Weaviate Cloud, GraphQL is switched off on December 1, 2026 for clusters that have not used it in the last 30 days, and on May 1, 2027 for all remaining clusters. New Weaviate Cloud clusters already start without GraphQL. Self-hosted Weaviate releases from before May 1, 2027 keep GraphQL; the first minor release after that turns it off by default.
What error will I see?
POST /v1/graphql and POST /v1/graphql/batch return HTTP 422 with the message "graphql api is disabled".
Am I affected if I use a current client?
Usually not. The current Python, TypeScript, Java and C# clients and the Go v6 client query over gRPC. Older clients, graphql_raw_query(), and anything that posts to /v1/graphql directly are affected. Python weaviate-client 4.4 to 4.10 and npm weaviate-client 3.0 to 3.3 still send aggregate queries through GraphQL.
Does n8n's Weaviate node break?
n8n's Weaviate vector store node connects over gRPC. An n8n workflow is affected only if an HTTP Request node posts to /v1/graphql. Paste the workflow JSON into the checker above to find those nodes.
How do I test before the switch-off?
On self-hosted Weaviate, set DISABLE_GRAPHQL=true (or the runtime setting disable_graphql) and run your tests. On Weaviate Cloud, create a new test cluster, which has GraphQL off, and point a staging copy of your app at it.
Is my code uploaded?
No. The check runs in your browser and only counts, anonymously, that a check ran and what the overall verdict was.
Sources: Weaviate's announcement (October 26, 2026) and migration guide. Workflow Exit is not affiliated with Weaviate. Other platforms and APIs closing in 2026 and 2027 are in the shutdown tracker.