--- title: Deprecating the GraphQL API: timeline and migration paths description: Weaviate is deprecating its GraphQL API as of October 26, 2026, moving to gRPC and REST instead. Nothing breaks immediately. Weaviate Cloud clusters keep... canonical: https://daily.dev/posts/deprecating-the-graphql-api-timeline-and-migration-paths-aik6hgmcl twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Deprecating the GraphQL API: timeline and migration paths | daily.dev og:description: Weaviate is deprecating its GraphQL API as of October 26, 2026, moving to gRPC and REST instead. Nothing breaks immediately. Weaviate Cloud clusters keep... og:url: https://daily.dev/posts/deprecating-the-graphql-api-timeline-and-migration-paths-aik6hgmcl og:image: https://api.daily.dev/og/posts/AIk6HgMcL.png og:image:alt: Deprecating the GraphQL API: timeline and migration paths og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Deprecating the GraphQL API: timeline and migration paths **[Weaviate](https://daily.dev/sources/weaviate)** · 8 min read · 0 upvotes · 0 comments ## Summary Weaviate is deprecating its GraphQL API as of October 26, 2026, moving to gRPC and REST instead. Nothing breaks immediately. Weaviate Cloud clusters keep GraphQL until May 1, 2027, the end-of-life date, though inactive clusters lose it earlier on December 1, 2026. Self-hosted users can test the change now by setting the DISABLE_GRAPHQL environment variable. Users on current Python, TypeScript, Java or C# clients are most likely not affected. gRPC offers faster binary queries, and the new APIs check access per collection. A REST Search API is available in Preview as a JSON alternative. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### When does Weaviate remove support for the GraphQL API? Weaviate's GraphQL API is deprecated as of October 26, 2026, but nothing breaks that day. Weaviate Cloud switches it off on inactive clusters (no GraphQL use in 30 days) on December 1, 2026, and on all remaining clusters by May 1, 2027, which is the official end-of-life date. Self-hosted versions keep working GraphQL until that date too, then disable it by default in the next minor release. _Teams planning the Weaviate GraphQL migration can track deprecation timelines like this on daily.dev._ ### How do I disable the GraphQL API on a self-hosted Weaviate instance to test my migration? Set the DISABLE_GRAPHQL environment variable to true and restart Weaviate, or set the runtime-config key disable_graphql. With GraphQL disabled, calls to POST /v1/graphql and POST /v1/graphql/batch return HTTP 422 with the message 'graphql api is disabled', letting you verify your application still works before the official cutoff. _Developers verifying API migrations before a deadline can follow guides like this on daily.dev._ ### What should I use instead of Weaviate's GraphQL API for search queries? Use the current Python, TypeScript, Java or C# client libraries, which search over gRPC and are the recommended path. For browsers or edge runtimes that cannot open a native gRPC connection, use the TypeScript web client (@weaviate/web) with gRPC-Web. For stacks that cannot run a client at all, a REST Search API offering plain JSON endpoints is available in Preview, though it covers only a subset of what GraphQL supported. _Developers choosing a replacement query API can compare these migration paths on daily.dev._ ## Similar posts on daily.dev - [GraphQL Explorer removal from API documentation on November 7, 2025](https://daily.dev/posts/graphql-explorer-removal-from-api-documentation-on-november-7-2025-ocavorsgd) · GitHub Changelog · 0 upvotes · 0 comments - [Weaviate 1.37 Release](https://daily.dev/posts/weaviate-1-37-release-nnexx0ui6) · Weaviate · 7 upvotes · 0 comments - [Scale Faster with Managed Weaviate: Now in Public Preview on DigitalOcean](https://daily.dev/posts/scale-faster-with-managed-weaviate-now-in-public-preview-on-digitalocean-dzpenirrp) · DigitalOcean · 0 upvotes · 0 comments - [Weaviate security release - High severity fix for credential disclosure in the Google modules](https://daily.dev/posts/weaviate-security-release---high-severity-fix-for-credential-disclosure-in-the-google-modules-7pwzanpuh) · Weaviate · 0 upvotes · 0 comments --- Tags: [#architecture](https://daily.dev/tags/architecture), [#graphql](https://daily.dev/tags/graphql), [#vector-search](https://daily.dev/tags/vector-search), [#grpc](https://daily.dev/tags/grpc), [#weaviate](https://daily.dev/tags/weaviate) [View this post on daily.dev](https://daily.dev/posts/deprecating-the-graphql-api-timeline-and-migration-paths-aik6hgmcl) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Deprecating the GraphQL API: timeline and migration paths","url":"https://daily.dev/posts/deprecating-the-graphql-api-timeline-and-migration-paths-aik6hgmcl","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/deprecating-the-graphql-api-timeline-and-migration-paths-aik6hgmcl"},"datePublished":"2026-10-26T12:57:51.370Z","dateModified":"2026-10-26T13:01:08.621Z","description":"Weaviate is deprecating its GraphQL API as of October 26, 2026, moving to gRPC and REST instead. Nothing breaks immediately. Weaviate Cloud clusters keep...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/1ea65b5044b53ded509678ab24f47729?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/1ea65b5044b53ded509678ab24f47729?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Weaviate","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Weaviate","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/07d0692410934a578c4d59e02f7ea685","url":"https://daily.dev/sources/weaviate"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/deprecating-the-graphql-api-timeline-and-migration-paths-aik6hgmcl","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"architecture,graphql,vector-search,grpc,weaviate","timeRequired":"PT8M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Weaviate","item":"https://daily.dev/sources/weaviate"},{"@type":"ListItem","position":3,"name":"Deprecating the GraphQL API: timeline and migration paths"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/deprecating-the-graphql-api-timeline-and-migration-paths-aik6hgmcl#faq","mainEntity":[{"@type":"Question","name":"When does Weaviate remove support for the GraphQL API?","acceptedAnswer":{"@type":"Answer","text":"Weaviate's GraphQL API is deprecated as of October 26, 2026, but nothing breaks that day. Weaviate Cloud switches it off on inactive clusters (no GraphQL use in 30 days) on December 1, 2026, and on all remaining clusters by May 1, 2027, which is the official end-of-life date. Self-hosted versions keep working GraphQL until that date too, then disable it by default in the next minor release. Teams planning the Weaviate GraphQL migration can track deprecation timelines like this on daily.dev."}},{"@type":"Question","name":"How do I disable the GraphQL API on a self-hosted Weaviate instance to test my migration?","acceptedAnswer":{"@type":"Answer","text":"Set the DISABLE_GRAPHQL environment variable to true and restart Weaviate, or set the runtime-config key disable_graphql. With GraphQL disabled, calls to POST /v1/graphql and POST /v1/graphql/batch return HTTP 422 with the message 'graphql api is disabled', letting you verify your application still works before the official cutoff. Developers verifying API migrations before a deadline can follow guides like this on daily.dev."}},{"@type":"Question","name":"What should I use instead of Weaviate's GraphQL API for search queries?","acceptedAnswer":{"@type":"Answer","text":"Use the current Python, TypeScript, Java or C# client libraries, which search over gRPC and are the recommended path. For browsers or edge runtimes that cannot open a native gRPC connection, use the TypeScript web client (@weaviate/web) with gRPC-Web. For stacks that cannot run a client at all, a REST Search API offering plain JSON endpoints is available in Preview, though it covers only a subset of what GraphQL supported. Developers choosing a replacement query API can compare these migration paths on daily.dev."}}]} ```