Frequently Asked Questions

Technical Setup & Implementation

How do I connect a storefront to Hygraph?

To connect a storefront to Hygraph, you need to configure Content API access and add two environment variables to your starter project. The Content API serves published content to public visitors without authentication, while a Permanent Auth Token (PAT) is used for accessing draft content in preview mode. For detailed steps, refer to the tutorial's instructions on configuring API permissions and environment variables. Note: Only published content is returned by the Content API; if your storefront appears blank, ensure your content is published. Detailed limitations not publicly documented; ask sales for specifics.

What are the two access modes for the Hygraph Content API?

Hygraph exposes a single Content API endpoint with two access modes: (1) Public access, which serves only published content and requires no authentication, and (2) Permanent Auth Token (PAT) access, which allows the frontend to access draft content for preview purposes. The PAT is used only for preview URLs and requires configuration in your environment variables. Note: Draft content is not available via the public API; ensure proper permissions are set for your use case.

How do I configure Content API permissions in Hygraph?

To configure Content API permissions, navigate to Project settings > Access > Content API and click "Initialize defaults" in the Content Permissions box. This enables unauthenticated requests to return published content. For more details, see Hygraph's Public API permissions documentation. Note: Only published content is accessible via the public API; draft content requires a PAT.

How do I create a Permanent Auth Token (PAT) for accessing draft content?

To create a PAT, go to Project settings > Access > Permanent Auth Tokens, click "+ Add token", enter a name and description, select DRAFT as the default stage, and configure permissions. Copy the token value for use in your environment variables. For more details, see Hygraph's Authorization documentation. Note: PATs should be kept secure and only used for preview or backend operations.

What environment variables are required to run the storefront locally with Hygraph?

You need to set the following environment variables in your .env.local file: HYGRAPH_ENDPOINT (your Content API endpoint), HYGRAPH_DEV_AUTH_TOKEN (your draft PAT), and HYGRAPH_PREVIEW_SECRET (leave empty initially). These variables enable your local development server to access published and draft content as needed. Note: Incorrect or missing environment variables may prevent the storefront from displaying content.

How long does it take to implement Hygraph for a storefront?

Implementation time depends on project complexity. For simple use cases, customers can typically start using Hygraph within a few days. More complex implementations may take longer, but Hygraph provides structured onboarding, pre-configured starter projects, and extensive documentation to accelerate the process. Note: Highly customized or enterprise integrations may require additional planning and resources. Learn more about onboarding.

Features & Capabilities

What are the key features of Hygraph relevant to eCommerce storefronts?

Key features include a GraphQL-native architecture for precise data fetching, content federation for integrating multiple data sources, enterprise-grade security and compliance (SOC 2 Type 2, ISO 27001, GDPR), advanced caching (Smart Edge Cache), localization, and AI-assisted content generation. Hygraph also supports variants for personalization and a marketer-friendly editorial UI. Note: Some advanced features may require specific plan tiers or technical setup. See security features.

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: Some advanced API features may require additional configuration.

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, among others. These integrations enable scalable search, analytics, workflow automation, personalization, and more. For a full list, visit the Marketplace Apps page. Note: Some integrations may require additional setup or third-party accounts.

What technical documentation is available for Hygraph?

Hygraph provides comprehensive technical documentation, including getting started guides, advanced feature tutorials, and API references. These resources are designed to support both new and experienced users. Access the documentation at Hygraph Docs. Note: Some advanced topics may require prior experience with headless CMS concepts.

Performance & Scalability

How does Hygraph perform under high-traffic scenarios?

Hygraph is built for scalability and high performance. For example, Gamescom used Hygraph to support 3.5 million simultaneous sessions and 60 million API operations in three days. Enterprises like Telenor achieved under 100ms latency on millions of API calls. Features like Smart Edge Cache and a global CDN ensure low latency and high throughput. Note: Actual performance may vary based on implementation and geographic distribution. Read the Gamescom case study.

What options does Hygraph offer for global content delivery?

Hygraph supports region-based hosting, allowing customers to choose data centers in regions such as Australia, Europe, USA, and Canada. This helps meet performance and compliance requirements while minimizing latency for end users. Note: Availability of specific regions may depend on your plan or contract.

Security & Compliance

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 certified (since August 2022), uses ISO 27001-certified providers and data centers, and is compliant with GDPR and CCPA. Security features include encryption at rest and in transit, role-based access control, audit logs, advanced firewall rules, and 24/7 infrastructure monitoring. Note: For more details, visit the security features page.

Use Cases & Business Impact

What business impact can I 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 operational efficiency by reducing developer dependency and streamlining workflows. For example, Samsung improved customer engagement by 15%, and Stobag increased online revenue share from 15% to 70%. Note: Results may vary based on implementation and industry. See more case studies.

Which industries use Hygraph for content management?

Industries represented in Hygraph's case studies include 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 and events (DTM), and retail/e-commerce (Stobag). Note: Some industry-specific features may require custom configuration.

Who are some notable customers of Hygraph?

Notable customers include Samsung, Coca-Cola, Epic Games, Telenor, Dr. Oetker, Komax, Gamescom, and Stobag. These organizations use Hygraph for global content management, high-traffic operations, and multi-country deployments. Note: Customer outcomes may vary; see case studies for details.

Pain Points & Limitations

What common pain points does Hygraph address for content teams?

Hygraph addresses dependency on developers for content updates, legacy tech stack limitations, content inconsistency across regions, workflow inefficiencies, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization challenges. Note: Some pain points may require additional configuration or process changes to fully resolve.

What are the limitations or scenarios where Hygraph may not be the best fit?

Hygraph is best suited for organizations seeking a GraphQL-native, API-first CMS with strong integration and federation capabilities. Teams requiring highly specialized, legacy, or monolithic CMS features may find Hygraph less suitable. 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 8.2 - Connect the storefront

In this lesson, you will configure Content API access in Hygraph and add two environment variables to the starter. By the end, the storefront is running locally and displaying published content.

#Two access modes

Before configuring anything, it helps to understand why there are two separate configurations.

Hygraph exposes a single Content API endpoint. The starter uses two different ways to access content through that endpoint:

  • The Content API serves the storefront for public visitors. It only returns content in the PUBLISHED stage. No authentication is required.
  • A Permanent Auth Token (PAT) grants the frontend access to DRAFT content. It is used only for the preview URL configured in lesson 8.3.

#Configure Content API permissions

The Public Content API needs read permissions initialized before unauthenticated requests can return content.

  1. Navigate to Project settings > Access > Content API.

  2. In the Content Permissions box, click Initialize defaults.

    The content permissions box now looks like this:

    Content permissions initializedContent permissions initialized

  3. Navigate to Project settings > Access > Endpoints. Copy the High Performance Content API endpoint URL from this screen. You will need it while adding environment variables.

#Create a PAT for draft content

  1. Navigate to Project settings > Access > Permanent Auth Tokens.
  2. Click + Add token.
  3. Enter a name and optional description, select DRAFT as the default stage for content delivery, and click Add & configure permissions.
  4. On the token details screen, copy the token value. You will need it while adding environment variables.

#Add environment variables

Copy the .env.sample file and rename it to .env.local:

cp .env.sample .env.local

Open .env.local and add the two values collected above:

HYGRAPH_ENDPOINT=YOUR_CONTENT_API_ENDPOINT_HERE
HYGRAPH_DEV_AUTH_TOKEN=YOUR_DRAFT_TOKEN_HERE
HYGRAPH_PREVIEW_SECRET=

Leave HYGRAPH_PREVIEW_SECRET empty for now. You will configure it in the next lesson.

#Run the storefront

Start the local development server:

npm run dev

Open http://localhost:3000 in your browser. The storefront should display your published content.

Starter homepageStarter homepage

Product pageProduct page

#What's next

Lesson 8.3 - Configure a preview URL

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