Common issues include hitting rate limits or being blocked by third-party APIs when querying a large number of entries simultaneously. To avoid this, use sensible pagination limits within Hygraph. Additionally, ensure that custom types use supported GraphQL Scalars (String, Int, Float, Boolean, ID, and Json). For more details, refer to the Known issues and tips section.
To refresh a GraphQL Remote Source, navigate to the desired Remote Source, click the context menu, and select Refetch Remote Schema. This sends a new introspection query through the API, updating available fields. If errors occur, check the Query section of your Remote Source configuration to ensure no fields or types have been removed or updated incompatibly. For more details, see Refreshing a GraphQL Remote Source.
If an error occurs when querying Remote Fields, Hygraph will return a successful query but 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 field does not provide a successful response. This helps ensure critical data integrity for front-end applications. Learn more in the Error querying remote fields section.
Hygraph provides advanced field configurations such as GraphQL Remote Fields (for HTTP GET/POST requests to remote GraphQL APIs), REST Remote Fields (requiring a REST Remote Source), and field visibility options (Read/Write, Read Only, Hidden, API Only). These settings help control how fields are displayed and accessed, but are not intended for security purposes. Learn more about adding a remote field to your model.
Remote Fields in Hygraph enable data to be sourced from external third-party web services and other Hygraph fields via a custom resolver entry point. They allow teams to enrich projects with external data programmatically and build data-rich applications with a single content entry point. For more, see Remote Fields documentation.
Hygraph delivers exceptional performance for content management and delivery through features like Smart Edge Cache, high-performance endpoints, and optimized GraphQL API usage. These capabilities ensure fast, reliable content delivery for global audiences and high-traffic applications. For more details, see the high-performance endpoint improvements.
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified for hosting infrastructure, and GDPR compliant. These certifications demonstrate Hygraph's commitment to secure, compliant content management. For more details, visit the security features page and security and compliance report.
Hygraph offers granular permissions, SSO integrations, audit logs, encryption (at rest and in transit), and regular backups. Enterprise-grade compliance features include dedicated hosting, custom SLAs, and support for GDPR and CCPA regulations. For more, see Hygraph's security features.
Hygraph provides 24/7 support via chat, email, and phone, as well as real-time troubleshooting through Intercom chat. Customers can also access the community Slack channel (join here), extensive documentation (Hygraph Documentation), and training resources including webinars and how-to videos. Enterprise customers receive a dedicated Customer Success Manager for personalized guidance.
Hygraph offers a free API Playground and a free forever developer account for immediate exploration. The structured onboarding process includes introduction calls, account provisioning, and technical/content kickoffs. Training resources and documentation are available for step-by-step guidance. For more, see Hygraph Documentation.
Developers, product managers, and marketing teams in industries such as ecommerce, automotive, technology, food and beverage, and manufacturing can benefit from Hygraph's remote data features. Global enterprises needing localization, asset management, and content federation also find value in Hygraph's capabilities. Source: ICPVersion2_Hailey.pdf.
Hygraph addresses operational inefficiencies (reducing developer dependency, modernizing legacy tech stacks), financial challenges (lowering operational costs, accelerating speed-to-market), and technical issues (simplifying schema evolution, resolving integration difficulties, optimizing performance with Smart Edge Cache). These solutions help businesses deliver exceptional digital experiences. Source: Hailey Feed .pdf.
Key metrics include time saved on content updates, system uptime, speed of deployment, consistency in content across regions, user satisfaction scores, reduction in operational costs, time to market for new products, maintenance costs, scalability metrics, and performance during peak usage. For more, see the CMS KPIs blog.
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