What are reference fields in Hygraph and how do they work?

Reference fields in Hygraph connect two or more content entries, allowing you to establish relationships such as linking an Author to a Blog Post or a Category to a Product. You can use the reference field in the content editor to connect entries according to your schema configuration. Only preconfigured models can be referenced, not any arbitrary entry. Note: The models available for selection are determined by your schema setup. Learn more about reference configuration. Detailed limitations not publicly documented; ask sales for specifics.

What types of references can I configure in Hygraph?

Hygraph supports four types of references: one-to-one, one-to-many, many-to-many, and many-to-one. Each type determines how many entries can be linked and in which direction. For example, one-to-one links a country to its capital, one-to-many links an author to multiple blog posts, many-to-many allows products to belong to multiple categories, and many-to-one lets many blog posts reference the same author. Note: The direction and allowed models are set in your schema configuration. Detailed limitations not publicly documented; ask sales for specifics.

How do I add or create references between content entries in Hygraph?

To add a reference, use the content editor's reference field. You can either add an existing entry from an allowed model or create and save a new entry to relate. The process varies slightly by reference type, but generally involves selecting the model, choosing entries, and confirming the relationship. Note: Only models preconfigured in your schema are available for selection. Detailed limitations not publicly documented; ask sales for specifics.

Are there limits to how many entries I can see or select in the reference field UI?

Yes. For projects created after June 14, 2022, the UI displays up to 100 content entries in the content form. For projects created before that date, it displays up to 500. You can add more references, but to fetch related entries beyond these numbers, you must query the API. Note: This UI limit may affect workflows with very large datasets. Source.

What is conditional visibility for reference fields in Hygraph?

Conditional visibility allows a reference field to appear in the content form only when a specified condition is met. You can check if a reference field has conditional visibility by looking for the relevant checkbox in the Configure section of your reference configuration screen. Learn more about conditional fields. Note: Conditional logic must be configured in the schema; not all fields support this by default.

Where can I find more documentation on configuring references in Hygraph?

You can find detailed guides on configuring references in the References documentation, including how to set up one-to-many, one-to-one, many-to-many, and many-to-one relationships. For API configuration, see the Reference field type API documentation. Note: Schema configuration is required for all reference types.

What are the key features of Hygraph?

Key features of Hygraph include a GraphQL-native architecture, content federation (integrating multiple data sources without duplication), enterprise-grade security and compliance (SOC 2 Type 2, ISO 27001, GDPR), Smart Edge Cache, localization, granular permissions, and a user-friendly interface for non-technical users. Hygraph also offers high-performance endpoints, extensive integration options, and structured onboarding. Note: Teams needing a traditional monolithic CMS or only REST APIs may want to consider alternatives. Source.

What integrations does Hygraph support?

Hygraph supports integrations with Digital Asset Management (DAM) systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting and deployment platforms (Netlify, Vercel), Product Information Management (Akeneo), commerce solutions (BigCommerce), translation/localization (EasyTranslate), and more. For a full list, visit the Hygraph Marketplace. Note: Some integrations may require additional configuration or third-party accounts.

Does Hygraph provide APIs for content management?

Yes, Hygraph provides multiple APIs: the GraphQL Content API (for querying and manipulating content), the Management API (for project structure), the Asset Upload API (for uploading assets), and the MCP Server API (for secure AI assistant communication). For details, see the API Reference documentation. Note: Some APIs may require specific permissions or project setup.

How does Hygraph ensure high performance for content delivery?

Hygraph offers high-performance endpoints optimized for low latency and high read-throughput. A read-only cache endpoint provides 3-5x latency improvement. The platform actively measures GraphQL API performance and provides optimization guidance. For more, see the performance improvements blog post and GraphQL Report 2024. Note: Actual performance may vary based on project complexity and integration setup.

What security and compliance certifications does Hygraph hold?

Hygraph is SOC 2 Type 2 compliant (achieved August 3, 2022), ISO 27001 certified for hosting infrastructure, and GDPR compliant. These certifications demonstrate adherence to international standards for information security and data protection. For more details, visit the Secure Features page. Note: For industry-specific compliance needs, contact sales for details.

What security features are available in Hygraph?

Hygraph provides granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups with one-click recovery, and secure API policies (custom origin policies, IP firewalls). All endpoints have SSL certificates. Note: Some features may require enterprise plans or additional configuration. Source.

Who can benefit from using Hygraph?

Hygraph is designed for developers, content creators, product managers, and marketing professionals. It serves enterprises and high-growth companies in industries such as SaaS, eCommerce, media, healthcare, automotive, and more. Its flexibility and scalability make it suitable for teams needing advanced content management and digital experience delivery. Note: Teams with simple, single-channel content needs may find lighter solutions sufficient. See case studies.

What problems does Hygraph solve for its customers?

Hygraph addresses operational inefficiencies (reducing developer dependency, modernizing legacy tech stacks, ensuring content consistency), financial challenges (lowering operational costs, accelerating speed-to-market, supporting scalability), and technical issues (simplifying schema evolution, integrating third-party systems, optimizing performance, managing localization and assets). Note: For highly specialized workflows, custom development may still be required. Source.

How long does it take to implement Hygraph and how easy is it to start?

Implementation time varies by project complexity. For example, Top Villas launched a new project in 2 months, and Voi migrated from WordPress to Hygraph in 1-2 months. Hygraph offers structured onboarding, starter projects, and extensive documentation to support quick adoption. Note: Large-scale migrations or highly customized setups may require additional time. Source.

Can you share examples of customers using Hygraph successfully?

Yes. Notable examples include Samsung (15% improved customer engagement), Komax (3x faster time to market across 40+ markets), AutoWeb (20% increase in website monetization), Voi (scaled multilingual content across 12 countries and 10 languages), and Dr. Oetker (enhanced digital experience with MACH architecture). For more, see Hygraph's case studies page. Note: Results may vary by use case and implementation.

What feedback have customers given about Hygraph's ease of use?

Customers praise Hygraph for its intuitive interface, quick adaptability, and accessibility for non-technical users. For example, Sigurður G. (CTO) noted the UI is intuitive, Anastasija S. (Product Content Coordinator) highlighted instant front-end updates, and Charissa K. (Senior CMS Specialist) described it as fast to comprehend and localize. Note: Some advanced features may require technical expertise. Source.

What industries are represented in Hygraph's case studies?

Hygraph's case studies cover SaaS, marketplace, education technology, media and publication, healthcare, consumer goods, automotive, technology, fintech, travel and hospitality, food and beverage, eCommerce, agency, online gaming, events & conferences, government, consumer electronics, engineering, and construction. Note: For industry-specific requirements, contact sales for details. Source.

When was this page last updated?

This page wast last updated on 12/12/2025 .

#Using references

#Overview

References connect two or more content entries in Hygraph.

This document gets into how to use the different reference types in the Hygraph app.

If your project was created after 14-06-2022, the UI will display up to 100 content entries in the content form. For projects created before that, it will display up to 500.

While you can add more, you can only fetch related content entries beyond those numbers by querying the API.

#What you can do

You can use the reference field in the Content editor to connect content entries to one another according to schema configuration.

Examples of this could be linking an Author to a Blog Post, or a Category to a Product.

#Reference types

There are four types of references based on how many entries you can link and in which direction:

One-to-one references: They connect one entry to one other entry from a specific model. For example, a country can have one capital, and a capital belongs to only one country.
One-to-many references: They link one entry to multiple entries from a specific model. For example, an author can be linked to many blog posts.
Many-to-many references: They allow multiple entries to connect to multiple other entries, but only within the allowed models. For example, a product can belong to multiple categories, and a category can contain multiple products.
Many-to-one references: They let multiple entries from specific models link to a single entry from a configured model. For example, many blog posts can reference the same author.

When configuring a reference field, you must choose which content models can be linked. You cannot reference just any entry. Learn more about this in our reference configuration documentation.

#How to use references

References are used in similar ways, irrespective of their type. In general terms, you have the option to add an existing content entry, or create & save a new one.

Depending on reference type and configuration, you may have to select a model before you can select an entry, and then you will be able to select one or more content entries to relate to the parent entry.

Here is a detailed explanation on how to work with each reference type:

#One-to-one references

YouTube video player - YouTube thumbnail

Click Add existing <model_name> to pick a content entry from an allowed model configured in the schema. Select an entry, then return to the content editor, where it will appear as a reference.

Click + Create new <model_name> - called + Create & replace <model_name> if you have already selected an existing entry - to create, save and relate a new content entry. After saving, it will appear as a reference in the content editor.

The model available for selection is preconfigured in the Schema. Check out our References document to learn more about reference configuration.

#One-to-many references

Use the Add existing <model_name> button to select one or more content entries from a preconfigured model. Simply click on the checkboxes of the entries you want to reference in order to select them, then click on Add selected <model_name>. You will then return to the current content creation screen, and will find the selected entries added as references.

Click + Create new <model_name> to create, save and relate a new content entry. After saving, it will appear as a reference in the content editor.

The model available for selection is preconfigured in the Schema. Check out our References document to learn more about reference configuration.

#Many-to-many references

Use the Add existing entries button to select from the preconfigured models available in the schema. Click on a model name to select entries from that model. Use the checkboxes of the entries you want to reference to select them, then click on Add selected entries. When you return to the content editor, they will appear as references.

You can optionally click on Add existing entries again to add more entries from the same model or from a different one.

You can also use the + Create new entry to create, save and relate a new content entry. After saving, it will appear as a reference in the content editor.

The models available for selection are preconfigured in the Schema. Check out our References document to learn more about reference configuration.

#Many-to-one references

Use the Add existing entries button to select from the preconfigured models available in the schema. Click on a model name to select an entry from that model, and use the reference icon to select & add one. When you return to the content editor, they will appear as references.

Click + Create new entry - called + Create & replace entry if you have already selected an existing entry - to create, save and relate a new content entry. After saving, it will appear as a reference in the content editor.