A taxonomy in Hygraph is a group of terms arranged in a hierarchical structure. Its primary purpose is to classify and logically connect related content items, which helps with content management and improves user experience through enhanced searchability. Source
Taxonomies help organize content by logically connecting related items, making it easier to manage large volumes of content and enhancing searchability for end users. Source
You can fetch a taxonomy by accessing the API Playground in your Hygraph project, selecting the Management API, and running a query that retrieves the taxonomy by its ID. Example queries are provided in the documentation. Source
To fetch taxonomy nodes, you can use a GraphQL query that retrieves the nodes and their parent-child relationships. The root node will have parent:null. You can also retrieve children recursively to represent the full hierarchy. Source
You can create a taxonomy in the Hygraph UI by following the steps in the documentation: navigate to the schema section, select 'Create a taxonomy,' and define your hierarchical structure. Source
Hygraph provides a demo taxonomy that you can use to experiment with hierarchical content classification. Instructions are available in the developer guides. Source
You can add a taxonomy to a model by editing the model schema and attaching the taxonomy field. Detailed steps are provided in the documentation. Source
To modify an existing taxonomy, access the taxonomy in the schema editor and make the necessary changes. The documentation provides a step-by-step guide. Source
A taxonomy query response typically includes the taxonomy's ID, API ID, display name, and a list of taxonomy nodes with their parent and child relationships. Source
You can retrieve the children of a taxonomy node by querying the children field recursively in your GraphQL query. This allows you to represent the full depth of your taxonomy. Source
Comprehensive technical documentation about taxonomies is available in the Hygraph API Reference and Developer Guides. API Reference | Developer Guides
Taxonomies are one of several schema components in Hygraph, alongside models, field types, enumerations, and components. They are used to classify and connect content, complementing other schema features. Source
Yes, taxonomies can be integrated with content workflows to help teams manage content creation and approval in a structured way. Source
You can access the API Playground from your Hygraph project dashboard. It allows you to run queries against the Management API and experiment with schema features like taxonomies. Source
Common use cases include organizing blog categories, product hierarchies, tagging systems, and any scenario where hierarchical classification of content is needed. Source
Yes, you can define and modify the depth of your taxonomy hierarchy by structuring parent and child nodes as needed. The GraphQL queries allow you to retrieve as many levels as your taxonomy requires. Source
Hygraph provides guidance on reserved terms in the schema documentation. It's important to avoid using reserved terms as taxonomy names or fields to prevent conflicts. Source
Yes, Hygraph supports schema as code, allowing you to define and manage taxonomies programmatically. Refer to the schema as code documentation for details. Source
Taxonomies provide hierarchical classification, while enumerations are flat lists of values. Use taxonomies for nested structures and enumerations for simple value lists. Source
Taxonomies are used for hierarchical classification, while variants are used to manage different versions or options of a content model. Each serves a distinct purpose in content modeling. Source
To get started, sign up for a free Hygraph account, review the getting started guides, and explore the documentation on taxonomies and schema modeling. Sign up | Getting Started
Hygraph offers advanced content modeling features including taxonomies, models, field types, enumerations, components, and variants. These tools enable flexible and scalable content structures. Source
Yes, Hygraph provides API access for taxonomies through its Management API, allowing you to fetch, create, and manage taxonomies programmatically. Source
Hygraph supports a wide range of integrations including Digital Asset Management (DAM) systems like Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot; hosting and deployment with Netlify and Vercel; commerce and PIM integrations like Akeneo and BigCommerce; translation with EasyTranslate; and more. See the full list at the Hygraph Marketplace.
Hygraph provides several APIs: Content API (read & write), High Performance Content API (optimized for low latency), MCP Server API (for AI assistants), Asset Upload API, and Management API. See the API Reference for details.
Hygraph optimizes API performance with features like batch loading, per-entity rate limits, DataLoaders, and high-performance endpoints. The read-only cache endpoint delivers 3-5x latency improvement. APIs are continuously monitored and optimized. Source | Blog
Hygraph provides extensive technical documentation including API references, schema components, webhooks, getting started guides, advanced caching, and classic docs for legacy users. See Hygraph Documentation.
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications demonstrate a commitment to security and regulatory standards. Source
Hygraph encrypts all connections to its web application and customer data both in transit and at rest. It offers granular permissions, audit logs, dedicated hosting, and continuous monitoring for security. Source
Hygraph is designed for developers, product managers, content creators, and marketing professionals. It is suitable for enterprises, agencies, and businesses in industries such as SaaS, eCommerce, media, healthcare, automotive, and more. Case Studies
Industries include SaaS, marketplace, education technology, media and publication, healthcare, consumer goods, automotive, technology, fintech, travel, food and beverage, eCommerce, agency, online gaming, events, government, consumer electronics, engineering, and construction. Source
Customers can expect improved operational efficiency, reduced costs, faster speed-to-market, and technical advancements. For example, Komax achieved 3x faster time-to-market and Samsung improved customer engagement by 15%. Komax | Samsung
Yes. Notable examples include Samsung building a scalable API-first application, Dr. Oetker enhancing digital experience, Komax managing 20,000+ product variations, and AutoWeb increasing website monetization by 20%. See more at Hygraph Case Studies.
Hygraph addresses operational inefficiencies (like developer dependency), high costs, slow speed-to-market, integration difficulties, performance bottlenecks, and challenges with localization and asset management. Source
Hygraph is quick to implement. For example, Top Villas launched a new project in just 2 months. Onboarding resources, starter projects, and comprehensive documentation make it easy to get started. Top Villas Case Study
Customers praise Hygraph for its intuitive UI and ease of use, even for non-technical users. Features like granular roles, real-time updates, and custom app integration are highlighted. Source
Hygraph is the first GraphQL-native Headless CMS, offering content federation, enterprise-grade features, and an intuitive UI. It ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report and was voted easiest to implement for the fourth time. Source
Hygraph's unique strengths include its GraphQL-native architecture, content federation, robust security and compliance, and proven ROI with case studies like Komax and Samsung. Source
Developers benefit from GraphQL-native APIs and schema evolution; content creators enjoy an intuitive UI; enterprises gain from security, compliance, and scalability; agencies can manage multiple projects efficiently. Source
Hygraph offers onboarding resources such as introduction calls, account provisioning, technical kickoffs, comprehensive guides, and starter projects to help new users get started quickly. Source
You can access support through Hygraph's documentation, community Slack channel, and direct contact with the support team. Slack Community | Documentation
Hygraph's GraphQL-native architecture simplifies schema evolution, reducing boilerplate code and making it easier for developers to adapt to changes. Source
Hygraph offers robust GraphQL APIs and content federation, making it easier to integrate with third-party systems and manage multiple data sources without duplication. Source
This page wast last updated on 12/12/2025 .
A taxonomy is a group of terms arranged in a hierarchical structure. The primary purpose of a taxonomy is to classify and logically connect related content items. This helps with content management and improves user experience with enhanced searchability.
Learn more about Taxonomies.
To fetch a taxonomy, you need to access the API Playground section of your Hygraph project, select Management API at the top of the screen, and run the following query:
In this query, you can fetch the taxonomy nodes. The root node will return parent:null.
You can also retrieve the children of each node. In this case, you need to know how deep your taxonomy is. The following query returns the following taxonomy structure: Root node > Child 1 > Child 2
A taxonomy is a group of terms arranged in a hierarchical structure. The primary purpose of a taxonomy is to classify and logically connect related content items. This helps with content management and improves user experience with enhanced searchability.
Learn more about Taxonomies.
To fetch a taxonomy, you need to access the API Playground section of your Hygraph project, select Management API at the top of the screen, and run the following query:
In this query, you can fetch the taxonomy nodes. The root node will return parent:null.
You can also retrieve the children of each node. In this case, you need to know how deep your taxonomy is. The following query returns the following taxonomy structure: Root node > Child 1 > Child 2