Frequently Asked Questions

Product Features & Capabilities

What is a top-level remote field in Hygraph, and how does it work?

A top-level remote field in Hygraph allows you to fetch external data directly from a remote source, independent of any content entry. For example, you can configure a REST remote field in the Query system model to retrieve review data for any product by passing a productSlug argument. This enables you to query external review data without migrating content or making separate API calls from the frontend. Note: Top-level remote fields are not dependent on Hygraph content entries and can be tested immediately after configuration. Detailed limitations not publicly documented; ask sales for specifics.

How does Hygraph's Content Federation feature help with data integration?

Hygraph's Content Federation enables integration of multiple data sources without duplication, ensuring consistent and efficient content delivery across channels. For example, you can use top-level remote fields to fetch external review data and combine it with internal content, streamlining workflows and reducing manual effort. Note: Content Federation is ideal for businesses managing content across multiple regions, brands, or systems. Best fit for teams needing unified content delivery; teams requiring deep customization of federation logic may want to consult technical documentation for edge cases.

Does Hygraph support both REST and GraphQL APIs?

Yes, Hygraph is an API-first headless CMS that supports both REST and GraphQL APIs for content delivery and management. This allows developers to integrate Hygraph with any frontend or application. For more details, see API documentation. Note: While both API types are supported, advanced features may require familiarity with GraphQL schema modeling.

What integrations are available with Hygraph?

Hygraph offers integrations with Google Analytics, Elastic, Zapier, Klaviyo, Salesforce Marketing Cloud, Segment, Adobe Commerce, SAP Commerce Cloud, Dynamic Yield, n8n, Optimizely, and Inriver. These integrations enable scalable search, analytics, workflow automation, personalized marketing, and product data management. For a full list, visit Marketplace Apps. Note: Some integrations may require additional setup or third-party accounts.

Technical Requirements & Documentation

Where can I find technical documentation and tutorials for Hygraph?

Hygraph provides comprehensive technical documentation and developer guides, including getting started tutorials, advanced features, and onboarding resources. Access the documentation at Getting Started and Hygraph Documentation. Note: Documentation is regularly updated; for legacy features, refer to Classic Docs.

How easy is it to implement Hygraph, and what resources are available for onboarding?

Implementation timelines vary by project complexity. Simple use cases can be started within a few days, while complex projects may take longer. Hygraph offers pre-configured starter projects, structured onboarding (including introduction calls and technical kickoffs), extensive documentation, training resources, and community support via Slack (slack.hygraph.com). Note: Custom implementations may require additional technical expertise.

Security & Compliance

What security and compliance certifications does Hygraph hold?

Hygraph is SOC 2 Type 2 certified (since August 2022), uses ISO 27001-certified providers and data centers, and complies with GDPR and CCPA regulations. Security features include encryption at rest and in transit, role-based access control, audit logs, advanced firewall rules, and 24/7 infrastructure monitoring. For more details, visit security features page. Note: Some compliance requirements may depend on customer configuration and regional hosting choices.

Performance & Scalability

How does Hygraph perform under high-traffic scenarios?

Hygraph's global CDN, region-based hosting, and Smart Edge Cache ensure fast and reliable content delivery. For example, Gamescom supported 3.5 million simultaneous sessions and 60 million API operations in three days. Telenor achieved under 100ms latency on millions of API calls. Note: Performance may vary based on implementation and geographic distribution; consult technical documentation for optimization tips.

Use Cases & Business Impact

What business impact can customers expect from using Hygraph?

Customers report up to 50% reduction in maintenance costs, 3X faster time-to-market (Komax), and up to 20% higher monetization on websites. Hygraph enables personalized and localized content delivery, improving customer engagement (Samsung saw a 15% improvement). Note: Actual results may vary based on project scope and implementation; consult case studies for detailed outcomes.

Which industries are represented in Hygraph's case studies?

Hygraph's case studies span technology (Samsung, Epic Games), consumer goods (Coca-Cola, Dr. Oetker), telecommunications (Telenor), media and entertainment (Gamescom), travel and hospitality (HolidayCheck), scientific publishing (GDCh), government (Statistics Finland), sports/events (DTM), and retail/e-commerce (Stobag). Note: Industry-specific requirements may affect implementation; consult relevant case studies for details.

Pain Points & Solutions

What common pain points does Hygraph address for its customers?

Hygraph addresses dependency on developers, legacy tech stacks, content inconsistency, workflow inefficiencies, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization challenges. For example, HolidayCheck eliminated developer bottlenecks, and Dr. Oetker manages content for 40 countries from a single platform. Note: Some pain points may require custom solutions; consult technical support for edge cases.

Customer Proof & Success Stories

Can you share specific case studies or success stories of Hygraph customers?

Samsung improved customer engagement by 15% using Hygraph. Komax achieved a 3x faster time-to-market. Gamescom supported 3.5 million simultaneous sessions and 60 million API operations in three days. Stobag increased online revenue share from 15% to 70%. Dr. Oetker manages content for 40 countries from a single platform. Telenor achieved under 100ms latency on millions of API calls. HolidayCheck reduced developer bottlenecks. For more, visit Hygraph Case Studies. Note: Results are project-specific; consult case studies for detailed metrics.

Target Audience & Use Cases

Who is the target audience for Hygraph?

Hygraph is designed for marketing and content teams, product managers, developers, engineers, and enterprise/IT teams. It is particularly suited for companies in technology, consumer goods, telecommunications, media, retail, e-commerce, and more. Note: Teams requiring highly specialized workflows may need custom configuration; consult sales for details.

Product Limitations & Trade-Offs

Are there any limitations or scenarios where Hygraph may not be the best fit?

Hygraph is best suited for teams seeking unified content delivery, high scalability, and modern API integration. Teams requiring deep customization of federation logic, highly specialized workflows, or legacy system compatibility may need to consult technical documentation or sales for specifics. Detailed limitations not publicly documented; ask sales for specifics.

LLM optimization

When was this page last updated?

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

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

#Lesson 5.3 - Add top-level remote fields

In this lesson, you will add a top-level remote field to the Query system model and run a test query to confirm the remote source is working correctly.

A top-level remote field fetches remote data outside the context of any model entry. Where the remote field added in lesson 5.2 only returns reviews for a specific product, a top-level remote field can return review data independently. This is useful for fetching all reviews, or for passing in an argument from the frontend rather than from a content entry.

#Add a top-level remote field

You will add the field to the Query system model using the same HyDemoAPI remote source.

Complete top-level remote field configurationComplete top-level remote field configuration

  1. Open the Query model in the Schema editor and from the right sidebar, add a REST remote field.

  2. Fill in the following information:

    FieldInput
    Display nameReviews
    API IDAuto-completed. Leave as is.
    Remote sourceHyDemoAPI is selected by default. Leave as is.
    MethodGET is selected by default. Leave as is.
    Return typeSelect Reviews from the dropdown
    Input argumentsClick + Add input argument to reveal the argument fields
    Input typeString
    API IDproductSlug
    Make field requiredSelect checkbox
    Path/api/reviews/product/{{args.productSlug}}

    The Path appends to the remote source base URL. The {{args.productSlug}} path argument is supplied by whoever runs the query: a frontend component, a developer testing in the API Playground, or any API client. This means the top-level remote field has no dependency on Hygraph content. It can be queried even if the Product model contains no entries at all.

    The remote field in lesson 5.2 works differently. Its path uses {{doc.productSlug}}, which pulls the productSlug value from the specific Product entry being queried. The top-level remote field removes that dependency entirely.

  3. Click Add to save.

#Test the top-level remote field

Because the top-level remote field is not connected to a content entry, it can be tested immediately without creating any content first.

  1. Navigate to the API Playground.

  2. Run the following query:

The response confirms the remote source is correctly configured. The Hygraph API returns external review data without any data migration and without a separate API call from the frontend. This is Content Federation working as intended.

The schema is now complete. Content creation starts in the next lesson.

#What's next

Lesson 6 - Content

Or, go to the Tutorial overview for the full lesson list.