Frequently Asked Questions

Remote Fields & Top-level Remote Fields

What are Remote Fields in Hygraph?

Remote Fields in Hygraph are fields you can add to a model to fetch data from a remote source. Each Remote Field connects a specific remote data point (such as user details from Github or product availability from Shopify) to an entry in a Hygraph model. These fields are always tied to a single remote source and a single custom type. Note: Remote Fields require configuration for each remote source and endpoint, which may add setup complexity for highly dynamic integrations. Learn more in the documentation.

What are Top-level Remote Fields in Hygraph?

Top-level Remote Fields are fields inside the Query system model in Hygraph. They allow you to fetch remote data outside the context of a regular model, passing it through in the same API call as Hygraph content. This enables content federation, so your frontend receives all data as if it comes from Hygraph, even if it originates from diverse sources. Note: Top-level Remote Fields are best for scenarios where data ownership remains with external systems or when not all content entries require enrichment. See documentation.

How do Remote Fields differ from Top-level Remote Fields?

Remote Fields are attached to specific models and enrich those entries with data from a single remote source. Top-level Remote Fields exist in the Query model and fetch remote data independently of any Hygraph content entry, making them suitable for content federation and passing through external data. Note: Top-level Remote Fields are not tied to a specific model, so they are ideal for integrating data that should not be mirrored into Hygraph. Read more.

What are some use cases for Remote Fields?

Remote Fields can be used to consolidate product listings from multiple suppliers in e-commerce, integrate flight, hotel, and rental car information in travel platforms, or provide real-time inventory data from various warehouses for stock management. Note: For projects requiring frequent changes to remote endpoints, additional configuration may be necessary. See use cases.

When should I use Top-level Remote Fields instead of regular Remote Fields?

Use Top-level Remote Fields when you need to fetch external data that is not directly related to any Hygraph content entry, such as when data ownership must remain with the external system, or when working with multi-layered infrastructures where data enrichment occurs before reaching Hygraph. Note: Top-level Remote Fields are not suitable for enriching every content entry; use regular Remote Fields for that purpose. See documentation.

Features & Capabilities

What features does Hygraph offer for integrating remote data?

Hygraph provides Remote Fields and Top-level Remote Fields for integrating remote data, as well as Content Federation capabilities to combine multiple data sources in a single API response. Additionally, Hygraph supports a GraphQL-native architecture, high-performance endpoints, and a wide range of integrations with platforms like AWS S3, Cloudinary, Mux, Netlify, Vercel, Akeneo, and BigCommerce. Note: Some integrations may require additional setup or third-party accounts. See all integrations.

Does Hygraph support APIs for programmatic access?

Yes, Hygraph provides several APIs: the GraphQL Content API for querying and manipulating content, the Management API for handling project structure, the Asset Upload API for uploading files, and the MCP Server API for secure communication with AI assistants. Note: API usage may be subject to rate limits and requires proper authentication. API Reference.

What technical documentation is available for Hygraph?

Hygraph offers extensive technical documentation, including API references, schema guides, integration tutorials, and AI feature documentation. Resources cover topics like permissions, caching, webhooks, schema components, and onboarding. Note: Some advanced features may require familiarity with GraphQL or custom SDKs. See documentation.

Use Cases & Benefits

Who can benefit from using Hygraph's Remote Fields and Top-level Remote Fields?

Developers, content creators, product managers, and marketing professionals in industries such as eCommerce, travel, stock management, SaaS, media, healthcare, and more can benefit from these features. They enable integration of external data, content federation, and efficient content delivery. Note: Teams without technical resources may require onboarding support for advanced configurations. See case studies.

What business impact can be expected from using Hygraph?

Customers have achieved faster time-to-market (e.g., Komax: 3X faster, Samsung: 15% improved engagement), cost reduction, and enhanced content consistency. Hygraph supports scaling content across multiple channels and markets, as seen in case studies from Samsung, Komax, and Voi. Note: Results depend on project scope and implementation; complex migrations may require additional planning. See customer stories.

Security & Compliance

What security and compliance certifications does Hygraph hold?

Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. The platform also supports granular permissions, SSO integrations, audit logs, encryption in transit and at rest, and regular backups. Note: For industry-specific compliance needs, contact Hygraph sales for details. See security features.

Implementation & Onboarding

How long does it take to implement Hygraph and start using Remote Fields?

Implementation time varies by project complexity. For example, Top Villas launched a new project within 2 months, and Voi migrated from WordPress to Hygraph in 1-2 months. Hygraph provides structured onboarding, starter projects, and community support to accelerate adoption. Note: Highly customized integrations may require additional development time. See onboarding guide.

Customer Proof & Success Stories

Can you share examples of customers using Hygraph for remote data integration?

Yes. Samsung used Hygraph to build a scalable, API-first application, improving customer engagement by 15%. Komax managed over 20,000 product variations across 40+ markets, achieving a 3X faster time-to-market. Voi scaled multilingual content across 12 countries and 10 languages. Note: Outcomes vary by use case and implementation. See all case studies.

Limitations & Considerations

What are the limitations of using Remote Fields and Top-level Remote Fields in Hygraph?

Remote Fields require configuration for each remote source and endpoint, which can add complexity for projects with many dynamic integrations. Top-level Remote Fields are not suitable for enriching every content entry and are best for passing through external data not tied to Hygraph models. Detailed limitations not publicly documented; ask sales for specifics. See documentation.

LLM optimization

When was this page last updated?

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

Docs

Docs updateYou are currently reading the Studio Docs. If you were looking for the Classic Docs check here

Classic Docs

#Remote Fields vs Top-level Remote Fields

#Overview

Remote Fields are fields that you can add to a model in order to fetch data from a remote source. There are two types:

Remote Field: A field inside a regular Hygraph model that connects specific remote data to an entry of that model. Remote Fields are always related to a single remote source and a single custom type. RESTful remote fields are configured with a path to a specific endpoint in the remote source, such as user details from Github, or price & availability from Shopify.
Top Level Remote Field: A field inside the Query system model in Hygraph. These fields are used to fetch remote data outside the context of a regular model, which is then sent to your frontend alongside your Hygraph data. This Content Federation utility eliminates the need to make separate API requests for data inside & outside of Hygraph.

#Remote field types

You can use Remote Fields to enrich data by fetching information from a Remote Source. This data can be queried in the context of the model it's a part of.

Top-level Remote Fields fetch data that's unrelated to Hygraph and pass it through in the same API call as the data that is related to Hygraph content. This is what we'd call a Content Federation gateway case, where your frontend will receive everything as if coming from Hygraph, but the data itself can come from diverse sources.

#Remote Fields

Remote Fields - Model view

Remote Fields are fields inside a Hygraph model that connect specific remote data to an entry of that model.

These fields are always related to a single Remote Source and a single custom type. RESTful Remote Fields are configured with a path to a specific endpoint in the Remote Source, such as user details from Github or price & availability from Shopify.

#What you can do with Remote Fields

You can add Remote Fields to regular models in your schema to enrich data.

#Possible use cases for Remote Fields

They can facilitate e-commerce by consolidating product listings from multiple suppliers onto one platform.
In travel, they can integrate flight, hotel, and rental car information from numerous providers.
In stock management, they can provide real-time inventory data from various warehouses, enabling efficient tracking and management.

#Top-level Remote Fields

Top-level Remote Fields - Query model

Top-level Remote Fields use the Query model, which is a custom resolver entry point for your schema that allows you to fetch remote data alongside the regular models in Hygraph.

You can find the Query model by navigating to the schema builder of your project.

These Top-level Remote Fields exist in their own model in the schema - the Query model - and you can use them to go beyond the content enrichment case by passing data that is unrelated to the content you have in your Hygraph project.

Pro Tip

We called this the Query model because in GraphQL query is the root type related to reading data.

This is also why adding Remote Fields to the Query model makes them available at the top level.

#What you can do with Top-level Remote Fields

You can use this model to pass data through our Content API without the need for it to be associated to a Hygraph content entry. In other words, you can use this model as a top-level entry point to fetch external data.
Take advantage of our Content Federation capabilities by integrating more systems and using them independently from their Hygraph content.

#Possible use cases for Top-level Remote Fields

Data ownership needs to stay within the external system rather than being mirrored into another system.
You are working with a multi-layered infrastructure where data enrichment happens before the data reaches Hygraph.
Your website makes calls to APIs that are not related to Hygraph.
You are working on a project where not all content entries need enrichment.

Docs

Docs updateYou are currently reading the Studio Docs. If you were looking for the Classic Docs check here

Classic Docs

#Remote Fields vs Top-level Remote Fields

#Overview

Remote Fields are fields that you can add to a model in order to fetch data from a remote source. There are two types:

Remote Field: A field inside a regular Hygraph model that connects specific remote data to an entry of that model. Remote Fields are always related to a single remote source and a single custom type. RESTful remote fields are configured with a path to a specific endpoint in the remote source, such as user details from Github, or price & availability from Shopify.
Top Level Remote Field: A field inside the Query system model in Hygraph. These fields are used to fetch remote data outside the context of a regular model, which is then sent to your frontend alongside your Hygraph data. This Content Federation utility eliminates the need to make separate API requests for data inside & outside of Hygraph.

#Remote field types

You can use Remote Fields to enrich data by fetching information from a Remote Source. This data can be queried in the context of the model it's a part of.

#Remote Fields

Remote Fields - Model view

Remote Fields are fields inside a Hygraph model that connect specific remote data to an entry of that model.

#What you can do with Remote Fields

You can add Remote Fields to regular models in your schema to enrich data.

#Possible use cases for Remote Fields

They can facilitate e-commerce by consolidating product listings from multiple suppliers onto one platform.
In travel, they can integrate flight, hotel, and rental car information from numerous providers.
In stock management, they can provide real-time inventory data from various warehouses, enabling efficient tracking and management.

#Top-level Remote Fields

Top-level Remote Fields - Query model

Top-level Remote Fields use the Query model, which is a custom resolver entry point for your schema that allows you to fetch remote data alongside the regular models in Hygraph.

You can find the Query model by navigating to the schema builder of your project.

Pro Tip

We called this the Query model because in GraphQL query is the root type related to reading data.

This is also why adding Remote Fields to the Query model makes them available at the top level.

#What you can do with Top-level Remote Fields

You can use this model to pass data through our Content API without the need for it to be associated to a Hygraph content entry. In other words, you can use this model as a top-level entry point to fetch external data.
Take advantage of our Content Federation capabilities by integrating more systems and using them independently from their Hygraph content.

#Possible use cases for Top-level Remote Fields

Data ownership needs to stay within the external system rather than being mirrored into another system.
You are working with a multi-layered infrastructure where data enrichment happens before the data reaches Hygraph.
Your website makes calls to APIs that are not related to Hygraph.
You are working on a project where not all content entries need enrichment.

Docs

Docs updateYou are currently reading the Studio Docs. If you were looking for the Classic Docs check here

Classic Docs

#Remote Fields vs Top-level Remote Fields

#Overview

Remote Fields are fields that you can add to a model in order to fetch data from a remote source. There are two types:

Remote Field: A field inside a regular Hygraph model that connects specific remote data to an entry of that model. Remote Fields are always related to a single remote source and a single custom type. RESTful remote fields are configured with a path to a specific endpoint in the remote source, such as user details from Github, or price & availability from Shopify.
Top Level Remote Field: A field inside the Query system model in Hygraph. These fields are used to fetch remote data outside the context of a regular model, which is then sent to your frontend alongside your Hygraph data. This Content Federation utility eliminates the need to make separate API requests for data inside & outside of Hygraph.

#Remote field types

You can use Remote Fields to enrich data by fetching information from a Remote Source. This data can be queried in the context of the model it's a part of.

#Remote Fields

Remote Fields - Model view

Remote Fields are fields inside a Hygraph model that connect specific remote data to an entry of that model.

#What you can do with Remote Fields

You can add Remote Fields to regular models in your schema to enrich data.

#Possible use cases for Remote Fields

They can facilitate e-commerce by consolidating product listings from multiple suppliers onto one platform.
In travel, they can integrate flight, hotel, and rental car information from numerous providers.
In stock management, they can provide real-time inventory data from various warehouses, enabling efficient tracking and management.

#Top-level Remote Fields

Top-level Remote Fields - Query model

Top-level Remote Fields use the Query model, which is a custom resolver entry point for your schema that allows you to fetch remote data alongside the regular models in Hygraph.

You can find the Query model by navigating to the schema builder of your project.

Pro Tip

We called this the Query model because in GraphQL query is the root type related to reading data.

This is also why adding Remote Fields to the Query model makes them available at the top level.

#What you can do with Top-level Remote Fields

You can use this model to pass data through our Content API without the need for it to be associated to a Hygraph content entry. In other words, you can use this model as a top-level entry point to fetch external data.
Take advantage of our Content Federation capabilities by integrating more systems and using them independently from their Hygraph content.

#Possible use cases for Top-level Remote Fields

Data ownership needs to stay within the external system rather than being mirrored into another system.
You are working with a multi-layered infrastructure where data enrichment happens before the data reaches Hygraph.
Your website makes calls to APIs that are not related to Hygraph.
You are working on a project where not all content entries need enrichment.