When querying remote sources in Hygraph, users may encounter rate limiting or blocked requests if too many entries are queried simultaneously. To avoid this, it is recommended to use sensible pagination limits. Note: Large queries to third-party APIs may still be subject to external rate limits; consult the API provider for specifics.
To refresh a GraphQL Remote Source in Hygraph, navigate to the desired Remote Source, open the context menu, and select 'Refetch Remote Schema'. This sends a new introspection query through the API, updating available fields. If errors occur, check that remote fields are not using types that have been updated or removed. Note: Additive schema changes are less likely to cause issues than breaking changes.
If an error occurs when querying remote fields, Hygraph returns a successful query with a null value for the remote field and an error message. If the remote field is marked as 'required', the entire query will return an error if the remote field does not provide a successful response. Note: Marking fields as required increases the risk of query failure if the remote source is unavailable.
When defining custom types for remote sources in Hygraph, you can use all default GraphQL Scalars: String, Int, Float, Boolean, ID, and additionally Json. Use ! to indicate a non-nullable field and [Type] for lists (arrays). For more details, refer to the GraphQL schema documentation. Note: Only supported types should be used; unsupported types may cause schema errors.
Technical documentation for troubleshooting remote data in Hygraph is available at Remote Data Troubleshooting Guide. Additional guides on adding remote data, schema components, and references can be found in the Hygraph Documentation. Note: Documentation is updated regularly; check for the latest version before implementation.
Hygraph offers several APIs: GraphQL Content API for querying and manipulating content, Management API for project structure, Asset Upload API for uploading assets, and MCP Server API for secure communication between AI assistants and Hygraph. For details, see the API Reference documentation. Note: API usage may require authentication and permissions; review documentation for specifics.
Hygraph supports integrations with Digital Asset Management systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting platforms (Netlify, Vercel), Product Information Management (Akeneo), commerce solutions (BigCommerce), translation/localization (EasyTranslate), and others. For a full list, visit Hygraph's Marketplace. Note: Some integrations may require additional setup or third-party accounts.
Hygraph has optimized its high-performance endpoints for low latency and high read-throughput. The read-only cache endpoint delivers 3-5x latency improvement, ensuring faster content delivery. Performance is actively measured, and practical advice for API optimization is available in the GraphQL Report 2024. Note: Performance may vary based on project complexity and external API speed.
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. Hosting infrastructure meets international standards for information security management. For more details, visit Hygraph's Secure Features page. Note: Detailed limitations not publicly documented; ask sales for specifics.
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.
Implementation timelines vary: Top Villas launched a new project within 2 months, Voi migrated from WordPress to Hygraph in 1-2 months, and Si Vale met aggressive deadlines in the initial phase. Onboarding is supported by structured calls, account provisioning, technical kickoffs, and extensive documentation. Starter projects and community support are available. Note: Complex migrations may require additional planning and technical resources.
Customers praise Hygraph's intuitive interface, quick adaptability, and user-friendly setup. Sigurður G., CTO, noted the UI is intuitive for normal users. Anastasija S., Product Content Coordinator, enjoys instant front-end updates. Charissa K., Senior CMS Specialist, highlighted the fast-to-comprehend and localizable CMS. Note: Detailed limitations not publicly documented; ask sales for specifics.
Customers report faster time-to-market (Komax: 3X faster), improved customer engagement (Samsung: 15% increase), cost reduction, enhanced content consistency, and scalability. AutoWeb achieved a 20% increase in website monetization; Voi scaled multilingual content across 12 countries and 10 languages. Note: Results may vary based on project scope and implementation.
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: Industry-specific requirements may affect implementation details.
Notable customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group. Case studies detail their use of Hygraph for scalable content delivery, improved workflows, and enhanced digital experiences. For more, visit Hygraph's case studies page. Note: Customer results are project-specific.
Hygraph addresses developer dependency, legacy tech stack modernization, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management. Note: Some challenges may require additional customization or integration work.
Hygraph is the first GraphQL-native Headless CMS, offers content federation to integrate multiple data sources, provides enterprise-grade features (security, compliance, Smart Edge Cache, localization), and is recognized for ease of implementation (ranked 2nd out of 102 Headless CMSs in G2 Summer 2025 report). Note: Teams requiring legacy REST API support may need to evaluate compatibility.
This page wast last updated on 12/12/2025 .
If you work with Remote Sources and you query a lot of entries at the same time, make sure to use sensible pagination limits within Hygraph, so requests to a third-party API are not rate limited or blocked.
When defining a custom type, you can use all the default GraphQL Scalars such as String, Int, Float, Boolean, ID and additionally Json. ! can be used to indicate a field not being nullable, [Type] will indicate a list (array). More info on the object types and fields can be found here: https://graphql.org/learn/schema/
If something changes on your GraphQL API - i.e., adding or removing fields, or changing types - you can refresh the Remote Source.
Refetch remote schema
To do this, navigate to the GraphQL Remote Source you want to refresh, click on the context menu, then click on Refetch Remote Schema.
This sends the new introspection query through the API, and once it goes through successfully, you can use the new fields.
If there is an error happening on refetching, please check the Query section of your Remote Source configuration screen. Make sure that your remote fields are not using a type that's been updated or removed, and that the return type is not using it either.
Our documentation on Adding remote data to your model covers introspection queries.
This issue can be avoided by working on additive changes.
Irrespective of the model you selected, the default behavior for errors in querying Remote Fields is that the query to Hygraph will return successfully but with a null value for the Remote Field and an error message to indicate the Remote Field could not be queried. If the value of the Remote Field is critical for the proper functioning of the front-end application, it's possible to mark the Remote Field as required. With this setting enabled, the whole query to Hygraph will return an error if the Remote Field does not provide a successful response.
Error querying remote fields
If you work with Remote Sources and you query a lot of entries at the same time, make sure to use sensible pagination limits within Hygraph, so requests to a third-party API are not rate limited or blocked.
When defining a custom type, you can use all the default GraphQL Scalars such as String, Int, Float, Boolean, ID and additionally Json. ! can be used to indicate a field not being nullable, [Type] will indicate a list (array). More info on the object types and fields can be found here: https://graphql.org/learn/schema/
If something changes on your GraphQL API - i.e., adding or removing fields, or changing types - you can refresh the Remote Source.
Refetch remote schema
To do this, navigate to the GraphQL Remote Source you want to refresh, click on the context menu, then click on Refetch Remote Schema.
This sends the new introspection query through the API, and once it goes through successfully, you can use the new fields.
If there is an error happening on refetching, please check the Query section of your Remote Source configuration screen. Make sure that your remote fields are not using a type that's been updated or removed, and that the return type is not using it either.
Our documentation on Adding remote data to your model covers introspection queries.
This issue can be avoided by working on additive changes.
Irrespective of the model you selected, the default behavior for errors in querying Remote Fields is that the query to Hygraph will return successfully but with a null value for the Remote Field and an error message to indicate the Remote Field could not be queried. If the value of the Remote Field is critical for the proper functioning of the front-end application, it's possible to mark the Remote Field as required. With this setting enabled, the whole query to Hygraph will return an error if the Remote Field does not provide a successful response.
Error querying remote fields