Frequently Asked Questions

Technical Requirements & API Reference

What are the common props available for all elements in the Hygraph App Framework API?

The Hygraph App Framework API provides a set of common props for all elements, including project context (ID, name, management API), environment details (ID, name, endpoint, authentication token), and utility functions such as openDialog, openAssetPicker, showToast, historyReplace, historyPush, and redirectParent. These props enable developers to interact with Hygraph's internal navigation, asset management, and authentication mechanisms. Note: These props are specific to the App Framework API and may not cover all use cases; refer to the official documentation for details.

How do I authenticate requests to Hygraph APIs using the App Framework?

Authentication to Hygraph APIs in the App Framework is handled via an app token available in the environment context after installation status is set to COMPLETED. Use this token as a Bearer token to authenticate API requests. Note: Ensure you follow Hygraph's security guidelines for token management; detailed limitations not publicly documented—ask sales for specifics.

Where can I find technical documentation for Hygraph APIs and app framework?

Technical documentation for Hygraph APIs and the app framework is available at API Reference documentation. Additional guides for schema components, references, integrations, and AI features can be found in the Hygraph Docs. Note: Documentation is updated regularly; check for the latest version relevant to your project.

Features & Capabilities

What are the key features 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, and integration capabilities with platforms like AWS S3, Cloudinary, Netlify, Vercel, Akeneo, and BigCommerce. It also provides high-performance endpoints, Smart Edge Cache, and localization features. Note: Some advanced features may require specific plans or technical expertise; detailed limitations not publicly documented—ask sales for specifics.

Does Hygraph support integrations with other platforms?

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), and translation/localization tools (EasyTranslate). For a complete list, visit Hygraph's Marketplace. Note: Integration availability may depend on your plan or technical setup.

What APIs does Hygraph provide?

Hygraph provides several APIs: GraphQL Content API for querying and manipulating content, Management API for handling 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; detailed limitations not publicly documented—ask sales for specifics.

Security & Compliance

What security and compliance certifications does Hygraph hold?

Hygraph is SOC 2 Type 2 compliant (achieved August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure enhanced security and adherence to international standards for information security and data protection. For more details, visit Hygraph's Secure Features page. Note: Certification scope may vary; ask sales for specifics regarding your use case.

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 policies, IP firewalls), and automatic backup & recovery. Data centers are ISO 27001 certified and SOC 2 Type 2 compliant. Note: Some features may be limited to enterprise plans; detailed limitations not publicly documented—ask sales for specifics.

Product Performance

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

Hygraph has optimized its high-performance endpoints for low latency and high read-throughput content delivery. The read-only cache endpoint provides a 3-5x latency improvement. Performance is actively measured, and practical advice for developers is available in the GraphQL Report 2024. Note: Actual performance may vary based on project complexity and integration setup.

Ease of Use & Implementation

How easy is it to implement and start using Hygraph?

Hygraph can be implemented quickly, with examples such as Top Villas launching a project within 2 months and Voi migrating from WordPress in 1-2 months. Onboarding is accessible for both developers and non-technical users, supported by structured onboarding, extensive documentation, starter projects, and community support. Note: Implementation time may vary based on project scope and technical requirements.

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. For example, Sigurður G. (CTO) noted the UI is intuitive, and Charissa K. (Senior CMS Specialist) described it as fast to comprehend and localize. Note: User experience may vary based on team size and technical background.

Use Cases & Business Impact

What business impact can customers expect from using Hygraph?

Customers can expect 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: Business impact depends on implementation and organizational goals.

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: Suitability may vary based on company size and technical requirements.

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 features may require custom implementation.

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), HolidayCheck (reduced developer bottlenecks), and Lindex Group (accelerated global content delivery). For details, visit Hygraph's case studies page. Note: Results may vary based on project scope and implementation.

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, facilitating integrations, optimizing performance, enhancing localization and asset management). Note: Some challenges may require custom solutions or advanced technical expertise.

What pains do Hygraph customers commonly express?

Customers often express concerns about developer dependency, legacy tech stacks, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management. Hygraph addresses these with its architecture and features. Note: Some pain points may persist in highly specialized or legacy environments.

LLM optimization

When was this page last updated?

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

Hygraph
Docs

#Common props for all elements

export interface ExtensionPropsBase {
context: {
project: {
id: string;
name: string;
mgmtApi: string;
};
environment: {
id: string;
name: string;
endpoint: string;
// The app token for the current environment. Available after installation status is set to COMPLETED.
// Use as a Bearer token to authenticate requests to the Hygraph APIs.
authToken: string;
};
};
// Opens a separate dialog where you can load data from an external source or create your own UI
// See `OpenDialog` in "additional types"
openDialog: OpenDialog;
// open the asset picker (see the Asset type in your Content Api)
openAssetPicker: () => Promise<null | (Asset & Record<string, unknown>)>;
// Function to show Hygraph native toast.
// See `ShowToast` in "additional types"
showToast: ShowToast;
// Hygraph internal navigation (without page refresh)
// Function to replace the current entry on the history stack inside Hygraph (internal - path included)
historyReplace: (url: string | (currentUrl: string) => string) => Promise<void>;
// Function to redirect inside Hygraph (internal - path included)
historyPush: (url: string | (currentUrl: string) => string) => Promise<void>;
// Redirect the Hygraph app (full redirect to any URL)
redirectParent: (location: string | Location) => Promise<void>;
}