GraphQL is an open-source data query and manipulation language for APIs, enabling precise data fetching and schema evolution. Hygraph leverages GraphQL to provide a flexible, production-ready API for content management, allowing users to build and query their content models efficiently. Learn more.
Hygraph's GraphQL API offers exact data fetching (no over/under fetching), strong schema and type safety, and content federation—combining multiple APIs into a single schema accessible to clients. These features streamline development and improve performance. Source.
Hygraph supports a wide range of field types including String, Rich Text, Integer, Float, Boolean, Date, DateTime, JSON, Asset, Color, Location, Enumeration, Reference (Simple & Union), and Remote fields. These enable flexible modeling of content for any use case. See full list.
Hygraph automatically generates queries for fetching single entries (e.g., post) and multiple entries (e.g., posts) for each content type. Example queries are provided in the cheatsheet.
Yes, you can query related entries (e.g., comments on posts) and fetch localized content for multiple locales in a single request. The default locale is en, but you can specify others as needed. Source.
Hygraph allows you to specify content stages (e.g., DRAFT, PUBLISHED) and fetch specific versions of entries at any point in time using version queries. This supports robust content workflows and auditing. Learn more.
Hygraph supports create, update, batch update, insert (connect), delete, and upsert mutations for content entries. These operations allow flexible management of content via GraphQL. See documentation.
Hygraph provides built-in filtering, ordering (using orderBy), and pagination arguments (first, last, skip, before, after) for content queries. These features enable efficient data retrieval. Filtering, Ordering, Pagination.
Yes, Hygraph supports the @skip and @include directives, as well as GraphQL variables for dynamic queries. This allows for flexible and conditional data fetching. Source.
You can start building with Hygraph's GraphQL API within minutes using the provided cheatsheet and documentation. Sign up for free or request a demo for larger projects. Cheatsheet, Sign up.
Yes, Hygraph's low-code API management layer and content federation features allow you to unify microservices and external APIs into a single schema, streamlining operations and reducing maintenance overhead. Learn more.
Hygraph supports any file type as assets, not just images. Assets are connected to models via reference fields and can be localized by default. Asset documentation.
Hygraph provides a flexible localization API, allowing you to publish content for all or specific locales in your project. This is ideal for global brands and multilingual content delivery. Localization docs.
Yes, you can create custom content stages in the Hygraph UI and query or publish content from these stages, supporting advanced publishing workflows. Content stages docs.
Hygraph supports batch mutations for updating multiple entries at once and upsert operations to create or update entries based on unique criteria. This enables efficient bulk content management. Mutations docs.
You can use the connect mutation to insert related entries at a specific position, reflecting relationships in your content model. This is useful for managing complex content structures. Source.
Yes, you can delete entries by specifying the unique criteria in the where argument. This operation is supported for flexible content management. Source.
Hygraph offers extensive technical documentation covering API reference, schema components, references, webhooks, and AI integrations. Access all resources at Hygraph Documentation.
Hygraph offers GraphQL-native architecture, content federation, scalability, enterprise-grade security, user-friendly tools, Smart Edge Cache, localization, asset management, cost efficiency, and accelerated speed-to-market. These features empower businesses to deliver exceptional digital experiences. Features.
Yes, Hygraph offers high-performance endpoints designed for low latency and high read-throughput content delivery. Performance improvements are detailed in the blog post.
Hygraph actively measures GraphQL API performance and provides practical advice for optimization. Best practices are shared in the GraphQL Report 2024 and the GraphQL Survey 2024.
Hygraph integrates with DAM systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), Adminix, Plasmic, and supports custom integrations via SDK and APIs. Explore more in the Marketplace and Integrations Documentation.
Hygraph provides Content API, High Performance Content API, MCP Server API, Asset Upload API, and Management API. Each serves different content, asset, and management needs. API Reference.
Hygraph allows uploading assets from file systems or remote URLs, supports DAM integrations, and provides unlimited asset storage on all plans. Asset management details are in the documentation.
Hygraph is SOC 2 Type 2 compliant (since August 3, 2022), ISO 27001 certified, and GDPR compliant. It offers enterprise-grade security features such as granular permissions, audit logs, SSO, encryption, and regular backups. Secure features.
Hygraph uses ISO 27001-certified providers, encrypts data at rest and in transit, provides audit logs, granular permissions, SSO, regular backups, and a customer reporting process for incidents. Learn more.
Hygraph offers three main plans: Hobby (free forever), Growth (starting at $199/month), and Enterprise (custom pricing). Each plan includes different features and limits. Pricing details.
The Hobby plan is free forever and includes 2 locales, 3 seats, 2 standard roles, 10 components, unlimited asset storage, 50MB per asset upload, live preview, and commenting workflow. Sign up.
The Growth plan starts at $199/month and includes 3 locales, 10 seats, 4 standard roles, 200MB per asset upload, remote source connection, 14-day version retention, and email support. Get started.
The Enterprise plan offers custom limits, version retention for a year, scheduled publishing, dedicated infrastructure, global CDN, security controls, SSO, multitenancy, instant backup recovery, custom workflows, dedicated support, and custom SLAs. Try Enterprise.
Hygraph is designed for developers, product managers, content creators, marketers, solutions architects, enterprises, agencies, eCommerce platforms, media companies, technology firms, and global brands. Its flexibility suits SaaS, eCommerce, media, healthcare, and more. Case studies.
Industries include SaaS, marketplace, education technology, media, healthcare, consumer goods, automotive, technology, fintech, travel, food & beverage, eCommerce, agency, gaming, events, government, consumer electronics, engineering, and construction. See all.
Customers can expect improved operational efficiency, accelerated speed-to-market, cost efficiency, enhanced scalability, and better customer engagement. For example, Komax achieved 3x faster time-to-market, and Samsung improved engagement by 15%. Case studies.
Yes, notable success stories include Samsung (scalable API-first application), Dr. Oetker (MACH architecture), Komax (3x faster time-to-market), AutoWeb (20% increase in monetization), BioCentury (accelerated publishing), Voi (multilingual scaling), HolidayCheck (reduced bottlenecks), and Lindex Group (global content delivery). Full list.
Implementation time varies by project. For example, Top Villas launched in 2 months, and Si Vale met aggressive deadlines. Hygraph offers a free API playground, developer account, structured onboarding, training, and community support for fast adoption. Top Villas, Docs.
Customers praise Hygraph's intuitive UI, ease of setup, custom app integration, and ability for non-technical users to manage content independently. Real-time changes and reduced bottlenecks are frequently cited. Try Headless CMS, Enterprise feedback.
Hygraph addresses developer dependency, legacy tech stacks, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, scalability issues, schema evolution complexity, integration difficulties, performance bottlenecks, and localization/asset management. Case studies.
Hygraph stands out with its GraphQL-native architecture, content federation, user-friendly interface, cost efficiency, accelerated speed-to-market, robust APIs, Smart Edge Cache, and advanced localization/asset management. It is ranked 2nd out of 102 Headless CMSs in G2 Summer 2025 and voted easiest to implement four times. G2 Report.
Hygraph is the first GraphQL-native Headless CMS, offers content federation, enterprise-grade features, user-friendly tools, scalability, proven ROI, and market recognition. Case studies show 3x faster launches and improved engagement. Case studies.
Notable customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Vision Healthcare, HolidayCheck, and Voi. See logos and details on the case studies page.
Hygraph provides a structured onboarding process, training resources (webinars, videos), extensive documentation, and a community Slack channel for support. Documentation, Slack.
API status is available at status.hygraph.com and changelog at hygraph.com/changelog.
This page wast last updated on 12/12/2025 .
Get started with building your own production ready GraphQL API within minutes using Hygraph. Here’s a cheatsheet to bring you up to speed!
GraphQL is an open-source data query and manipulation language for APIs, and a runtime for fulfilling queries with existing data. Maintained and developed primarily via the GraphQL Foundation, GraphQL has had incredible adoption across a variety of verticals and use cases with organizations like Twitter, Facebook, Expedia, Shopify, and Hygraph to name a few.
Data Fetching: GraphQL gives you exactly what you ask for. No over or under fetching.
Schema & Type Safety: GraphQL uses a strongly typed system to define the capabilities of an API.
Content Federation: GraphQL can combine multiple APIs into a single schema to make it accessible to the client.
Embrace a low-code API management layer approach to unify your microservices and operations, and focus on growing your business model rather than maintaining it.
A string is just a simple string field. Hygraph supports single-line text, multi-line text, markdown and slug, as string variants.
The Rich Text field is an advanced string field that returns your content in raw, html, markdown and text.
Integers are whole numbers, and are often used to reference price in cents, stock quantities etc.
Floating point numbers represent fractional values with precision, such as distance, weight, volume, etc.
Booleans are used for entries that should have a true or false value.
The Date field type adheres to ISO 8601 standard. This means, October 7, 1989 is represented as 1989-10-07.
he DateTime field type also adheres to ISO 8601 standard, allowing you to set specific times on dates.
Often used for storing large amounts of data, this field could be seen as an “escape hatch” that could lose you some GraphQL benefits.
Assets are connected to models through a reference field. Assets can be any file type, not just images.
The Color field stores values that can be retrieved in several formats like HEX, RGBA, and CSS color values.
The Location field type returns latitude, longitude, and distance Float values.
Enums are a predefined list of values inside your GraphQL schema, and can be referenced by any content models.
Relations allow you to connect multiple models. In Hygraph they come as one-way or two-way references.
GraphQL Union Types (or Polymorphic Relations) allow you to define a list of possible relations, and decide which one to use.
Remote fields allow you to programmatically bring external data into your graph, without copying them into the CMS.
Hygraph automatically generates queries for fetching single, and multiple entries for each defined content type belonging to your project.
The post query is what you would use to fetch a single entry from the CMS.
{post(where: { id: "..." }) {idtitle}}
The posts query is what you would use to fetch multiple entries from the CMS.
{posts {id}}
Imagine posts have a one to many relation with comments. With GraphQL you can query the related comments in the same request.
{posts {idcomments {idauthor}}}
When fetching one or more entries, you can also fetch the localized entries. The default locale is set to en.
{post(where: { id: "..." }, locales: [en, fr, de]) {title}posts(locales: [en, fr, de]) {title}}
When fetching entries, you can also specify the content stage. The default content stage is set to DRAFT.
{post(where: { id: "..." }, stage: PUBLISHED) {title}posts(stage: PUBLISHED) {title}}
You can fetch all data of a specific entry at a point in time using the automatically generated version query.
{postVersion(where: { id: "abc123", revision: 1, stage: PUBLISHED }) {idrevisiondata}}
It is also possible to pass multiple arguments at a time. Let’s get the first 3 published posts by time, where the title contains "Hygraph".
{posts(where: { title_contains: "Hygraph" }orderBy: createdAt_DESCfirst: 3stage: PUBLISHED) {id}}
Multiple queries can be executed in parallel via a single request to your endpoint. Let's fetch our a single, and multiple posts in one request.
{post(where: { id: "..." }) {idtitle}posts {idtitle}}
We support both the @skip and @include directives for use in your schema.
query ($includeAuthor: Boolean!) {posts {idtitleauthor @include(if: $includeAuthor) {name}}}
It's recommended you use GraphQL variables when working with queries that use any variable data values.
query GetPostBySlug($slug: String!) {post(where: { id: $id }) {idtitle}}
Your project endpoint exposes GraphQL mutations. The mutations API allows you to interact with content ouside of Hygraph using GraphQL.
When creating new content entries, the data argument will have an associated input type that is specific to your content model.
mutation {createProduct(data: {name: "Face Mask",slug: "face-mask",price: 1000 }) {idnameslugprice}}
When updating single content entry, you must specify the unique where criteria of which you want to update, as well as the new data.
mutation {updateProduct(where: { id: "ckgcd5hzc01wd0a446vd3kqrs" }data: { price: 100 }) {idnameprice}}
Hygraph supports batch mutations that can be applied to "many" entries at once. They comply with Relay connection type specification.
mutation {updateManyProductsConnection(where: { featured: true }data: { featured: false }) {edges {node {featured}}}}
When inserting related entries, you can connect entries at a given position. The position of entries reflects that fetching relations.
mutation {updateAuthor(where: { id: "..." }data: { posts: { connect: { position: { before: "..." } } } }) {id}}
Similar to updating, and upserting entries, you can specify using where the entries you want to delete.
mutation {deleteProduct(where: { id: "..." }) {idnameslugprice}}
The upsert mutation allows you to create, or update a content entry based on whether the unique where values exist.
mutation {upsertProduct(where: { slug: "face-mask" }upsert: {create: { name: "Face Mask", slug: "face-mask", price: 1000 }update: { name: "Face Mask", slug: "face-mask", price: 1000 }}) {idnameslugprice}}
Hygraph creates filters for types you add to models. These filters can be applied to single or multiple entries, and nested object fields.
When fetching multiple entries you can use the orderBy argument to define the order of the returned records.
Hygraph supports various arguments for paginating content entries such as first, last, skip, before, and after.
You can create your own content stages inside the Hygraph UI, and query content from these stages, as well as publish to.
Hygraph boasts a flexible localization API that you can use to publish content for all or specific locales in your project.
The Asset model can be modified with custom Field Types, and are localized by default, but cannot be deleted.