Frequently Asked Questions

UI Extensions & API Reference

What is the purpose of the Field Extension API in Hygraph?

The Field Extension API in Hygraph allows developers to create custom UI extensions for fields within the CMS. It provides access to field properties such as name, locale, entryId, value, and event handlers (onBlur, onChange, onFocus), as well as metadata and configuration options. This enables tailored user experiences and advanced workflows for content editors. Note: UI extensions require familiarity with Hygraph's schema and API structure; detailed limitations not publicly documented—ask sales for specifics.

What properties and methods are available in the FieldExtensionProps interface?

The FieldExtensionProps interface includes properties such as name, locale, entryId, isTableCell, value, meta (active, error, touched), form, field (id, apiId, description, displayName, isList, isLocalized, isRequired, isUnique, isPreview, type), model, extension (config, fieldConfig, tableConfig), isExpanded, and expand. Methods include event handlers for onBlur, onChange, and onFocus. Note: This interface is specific to Hygraph Classic UI extensions; newer features may differ.

Features & Capabilities

What are the key capabilities and benefits of Hygraph?

Hygraph offers a GraphQL-native architecture, content federation, enterprise-grade security and compliance, user-friendly tools for non-technical users, scalability, high-performance endpoints, and integration capabilities with platforms like DAM, hosting, and commerce solutions. It is recognized for its ease of implementation, ranking 2nd out of 102 Headless CMSs in the G2 Summer 2025 report. Note: Best fit for teams seeking modern, API-first content management; teams requiring legacy CMS features may need to evaluate compatibility. Source

Does Hygraph support integration with other platforms and tools?

Yes, Hygraph supports integrations with Digital Asset Management 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 complete list, visit Hygraph's Marketplace. Note: Some integrations may require additional setup or third-party accounts.

What APIs does Hygraph provide?

Hygraph offers multiple APIs: GraphQL Content API (for querying and manipulating content), Management API (for project structure via Management SDK), Asset Upload API (for uploading assets), and MCP Server API (for secure communication between AI assistants and Hygraph). Detailed documentation is available at API Reference. Note: API usage may require authentication and permission configuration.

Product Performance & Technical Requirements

How does Hygraph perform in terms of content delivery and API response times?

Hygraph's high-performance endpoints are optimized 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 documented in the GraphQL Report 2024. Note: Actual performance may vary based on project complexity and integration setup. Source

Where can I find technical documentation for Hygraph?

Technical documentation is available for APIs, schema components, references, integrations, AI features, and onboarding guides. Key resources include the API Reference, Components Documentation, Getting Started, and integration guides for platforms like Mux and Akeneo. Note: Documentation for Hygraph Classic and newer versions may differ; verify compatibility before implementation.

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. Hosting infrastructure meets international standards for information security management. For more details, visit Hygraph's Secure Features page. Note: Compliance requirements may vary by region; verify with your legal team for specific needs.

What security features are available in Hygraph?

Hygraph offers granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption (in transit and at rest), regular backups with one-click recovery, secure API policies (custom origin, IP firewalls), and SSL certificates for all endpoints. Data centers are ISO 27001 certified and SOC 2 Type 2 compliant. Note: Some features may require enterprise plans or additional configuration. Source

Implementation & Ease of Use

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

Implementation timelines vary: Top Villas launched a new project within 2 months; Voi migrated from WordPress to Hygraph in 1-2 months. Onboarding is streamlined with structured calls, account provisioning, technical kickoffs, starter projects, and extensive documentation. Non-technical users can set up and use Hygraph easily, as highlighted in customer reviews. Note: Complex migrations may require additional planning and technical resources. Source

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

Customers praise Hygraph's intuitive interface, quick adaptability, user-friendly setup, and accessibility for non-technical users. Reviews highlight instant visibility of changes, clear setup, and granular roles/permissions that prevent mistakes. For example, Sigurður G. (CTO) noted the UI is intuitive for normal people; Charissa K. described it as "fast to comprehend and localizeable CMS." Note: Some advanced features may require technical expertise. Source

Use Cases & Business Impact

What business impact can customers expect from using Hygraph?

Customers report faster time-to-market (Komax achieved 3X faster launches), improved customer engagement (Samsung saw a 15% increase), cost reduction, enhanced content consistency, scalability, and proven ROI (AutoWeb increased website monetization by 20%). Note: Results depend on project scope and implementation quality. Source

Who is the target audience for Hygraph?

Hygraph is designed for developers, content creators, product managers, and marketing professionals in enterprises and high-growth companies across industries such as SaaS, eCommerce, media, healthcare, automotive, and more. Note: Teams with legacy CMS requirements should verify feature compatibility before migrating.

What industries are represented in Hygraph's case studies?

Hygraph's case studies span 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 complexity. Source

Customer Proof & Success Stories

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

Yes, notable examples include Samsung (15% improved engagement), Dr. Oetker (enhanced digital experience), Komax (3x faster time to market), AutoWeb (20% increase in monetization), BioCentury (accelerated publishing), Voi (scaled multilingual content across 12 countries), HolidayCheck (reduced developer bottlenecks), and Lindex Group (accelerated global content delivery). For details, visit Hygraph's case studies page. Note: Outcomes vary by project and team expertise.

Pain Points & Problems Solved

What core problems does Hygraph solve?

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, enhancing localization and asset management). Note: Teams with highly customized legacy workflows may require additional migration planning. Source

What pains do customers express before adopting Hygraph?

Customers often face developer dependency, legacy tech stack challenges, content inconsistency, workflow inefficiencies, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management struggles. Hygraph addresses these with its GraphQL-native architecture, content federation, and user-friendly tools. Note: Some pain points may persist if not fully addressed during migration. Source

LLM optimization

When was this page last updated?

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

Hygraph
Classic Docs

#Field extension API reference

function useFieldExtension(): FieldExtensionProps;
export interface FieldExtensionProps extends ExtensionPropsBase {
// name of the field in the form (may differ from the field apiId, ie. for localized fields)
name: string;
// current locale on localized field
locale?: string;
// id of the current entry, null on a new entry.
entryId: string | null;
isTableCell: boolean;
value: any;
onBlur: <T extends HTMLElement = HTMLElement>(
event?: FocusEvent<T>,
) => Promise<void>;
onChange: <T extends HTMLElement = HTMLElement>(
event: ChangeEvent<T> | any,
) => Promise<void>;
onFocus: <T extends HTMLElement = HTMLElement>(
event?: FocusEvent<T>,
) => Promise<void>;
// @see https://final-form.org/classic-docs/react-final-form/types/FieldRenderProps
meta: {
active: boolean;
error: any;
touched: boolean;
};
// access to the form state and other form fields
form: Form;
// details about the current field
field: {
id: string;
apiId: string;
description: string | null;
displayName: string;
isList: boolean;
isLocalized?: boolean;
isRequired?: boolean;
isUnique?: boolean;
// true when in version or stage comparison view
isPreview: boolean;
type: FieldExtensionType;
};
// details about the current model
model: Model;
// configuration of the extension.
extension: {
config: Record<string, any>;
fieldConfig: Record<string, any>;
tableConfig: Record<string, any>;
};
// whether the field is currently in fullscreen mode
isExpanded: boolean;
// set fullscreen mode
expand: (expand: boolean | ((isExpanded: boolean) => boolean)) => void;
}