Frequently Asked Questions

API Playground & Mutations

What mutations are available for managing products in Hygraph's API Playground?

Hygraph's API Playground supports several mutations for product management, including createProduct, updateProduct, publishProduct, unpublishProduct, and deleteProduct. These mutations allow users to create, update, publish, unpublish, and delete product entries directly from the API Playground. Note: Only mutations explicitly listed in the documentation are supported; custom mutations may require additional schema configuration.

How do I create a product using Hygraph's API Playground?

To create a product, use the createProduct mutation with fields such as productName, productSlug, productPrice, and related product attributes. The mutation will add the product entry in the DRAFT stage. For detailed mutation structure, refer to the lesson documentation. Note: The mutation requires a properly configured schema; missing fields or incorrect types may result in errors.

How can I update an existing product in Hygraph?

Use the updateProduct mutation, specifying the unique identifier (such as productSlug or ID) and the fields to update. The mutation will modify the product entry in the content editor. Note: Updates require a unique identifier; ambiguous or missing identifiers will prevent the mutation from executing.

How do I publish or unpublish a product in Hygraph?

To publish a product, use the publishProduct mutation with the product's unique identifier and specify the PUBLISHED stage. To unpublish, use the unpublishProduct mutation, specifying the product and the PUBLISHED stage to revert it to DRAFT. Note: Publishing and unpublishing require correct stage and identifier inputs; errors may occur if stages are misapplied.

How do I delete a product entry in Hygraph?

Use the deleteProduct mutation, providing the unique identifier (such as productSlug). After deletion, verify the removal by querying the products list or checking the content editor. Note: Deleted entries cannot be recovered unless backups are enabled; ensure you have backup and recovery options if needed.

What is the API Playground in Hygraph used for?

The API Playground in Hygraph is an interactive environment for running queries and mutations, allowing users to test and verify API operations in real time. It is especially useful for practicing mutations and checking responses before integrating with a frontend. Note: The API Playground is best suited for development and testing; production operations should use proper API endpoints and authentication.

Features & Capabilities

What APIs does Hygraph provide?

Hygraph offers multiple APIs, including the GraphQL Content API for querying and manipulating content, the Management API for project structure, the Asset Upload API for uploading files, and the MCP Server API for secure AI assistant communication. For detailed API documentation, visit Hygraph's API Reference. Note: API usage requires proper authorization and may be subject to rate limits.

What integrations are available with Hygraph?

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 other tools (Adminix, Plasmic). For a full list, visit Hygraph's Marketplace. Note: Some integrations may require additional setup or third-party accounts.

What technical documentation is available for Hygraph?

Hygraph provides extensive technical documentation, including API references, schema guides, onboarding tutorials, classic docs, integration guides, and AI feature documentation. Key resources are available at Hygraph Documentation. Note: Documentation is updated regularly; check for the latest guides before starting new projects.

Product Performance & Security

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

Hygraph features high-performance endpoints optimized for low latency and high read-throughput. The read-only cache endpoint delivers 3-5x latency improvement. Performance is actively measured and reported in the GraphQL Report 2024. Note: Actual performance may vary based on project complexity and integration setup.

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. Security features include granular permissions, SSO integrations, audit logs, encryption in transit and at rest, regular backups, and secure API policies. For more details, visit Hygraph's Secure Features page. Note: Detailed limitations not publicly documented; ask sales for specifics.

Ease of Use & Implementation

How easy is it to implement and start using Hygraph?

Implementation timelines vary: Si Vale met aggressive deadlines, Top Villas launched in 2 months, and Voi migrated from WordPress in 1-2 months. Onboarding is supported by structured calls, account provisioning, technical kickoffs, starter projects, and extensive documentation. Users can sign up for a free account at Hygraph Signup. Note: Complex projects may require additional customization and technical support.

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

Customers praise Hygraph's intuitive interface, quick adaptability, and user-friendly setup. Sigurður G. (CTO) noted the UI is intuitive for non-technical users. Anastasija S. (Product Content Coordinator) highlighted instant front-end updates. Charissa K. (Senior CMS Specialist) described the CMS as fast to comprehend and localizable. Note: Some advanced features may require technical expertise; onboarding resources are available for support.

Use Cases & Business Impact

What business impact can customers expect from using Hygraph?

Hygraph enables 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 monetization by 20%, Voi scaled multilingual content across 12 countries). Note: Results depend on project scope and implementation; detailed limitations not publicly documented.

What industries are represented in Hygraph's case studies?

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 features may require additional configuration.

Who are some of Hygraph's customers and what are their success stories?

Notable customers include Samsung (15% improved engagement), Dr. Oetker (enhanced digital experience), Komax (3x faster time to market), AutoWeb (20% monetization increase), BioCentury (accelerated publishing), Voi (multilingual scaling), HolidayCheck (reduced developer bottlenecks), and Lindex Group (accelerated global delivery). For more, visit Hygraph's case studies page. Note: Success metrics are project-specific; detailed limitations not publicly documented.

Pain Points & Problems Solved

What core problems does Hygraph solve for its customers?

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 pain points may require custom solutions; detailed limitations not publicly documented.

Product Information & Differentiators

What are the key capabilities and benefits of Hygraph?

Hygraph offers GraphQL-native architecture, content federation, enterprise-grade features (security, compliance, performance), user-friendly tools, scalability, proven ROI, high-performance endpoints, training/support, integration capabilities, and market recognition (ranked 2nd out of 102 Headless CMSs in G2 Summer 2025). Note: Best fit for teams seeking modern content management; teams needing legacy CMS features may want to consider alternatives.

What features differentiate Hygraph from other CMS platforms?

Hygraph is the first GraphQL-native Headless CMS, offers content federation, enterprise-grade features (Smart Edge Cache, localization, granular permissions), user-friendly tools, scalability, and proven ROI (Komax 3X faster time to market, Samsung 15% engagement improvement). Ranked 2nd in G2 Summer 2025 for ease of implementation. Note: Teams requiring legacy CMS workflows may need to evaluate compatibility.

LLM optimization

When was this page last updated?

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

Help teams manage content creation and approval in a clear and structured way
Hygraph
Docs
You are currently reading the Studio Docs. If you were looking for the Classic Docs check here

#6.2 Exercises - Mutations

#Overview

In this lesson, we'll use the following mutations, which Hygraph created automatically when we created our Product model:

  • createProduct
  • updateProduct
  • publishProduct
  • unpublishProduct
  • deleteProduct

#createProduct

First, we will create a product with the productName “My latest product” and the productSlug “my-latest-product” using the createProduct mutation.

Our mutation looks like this:

If we go to the Content editor, we'll see our new entry created there, in the DRAFT stage.

createProduct mutationcreateProduct mutation

#updateProduct

Next, we'll use an updateProduct mutation to change the productName to “Updated product”. In order to identify the entry we want to update, we need to provide a unique identifier. We could use the entry ID, as it is unique, but for this tutorial we'll use the slug, which we configured to be unique when we added the field to the Product model.

Let's try this mutation:

updateProduct mutationupdateProduct mutation

We can update any product, not just newly created products. Let's try updating the Black leather shoes product:

updateProduct mutation - example 2updateProduct mutation - example 2

#publishProduct

Now that our product contains the latest update, we should move it from the DRAFT stage to PUBLISHED;

publishProduct mutationpublishProduct mutation

We'll use the publishProduct mutation for that, along with our product Slug to publish our product:

If we go to the content editor, we'll be able to see it's now published:

Published productPublished product

#unpublishProduct

To unpublish it, we'll use the unpublishProduct mutation:

And we can also see this change in the content editor:

Unpublished productUnpublished product

#deleteProduct

If we want to delete this product, we'll use the deleteProduct mutation:

We can run a quick query to check if the product was deleted. Create a new query in the API playground and paste in the following:

You can also check the content editor, where you'll see that there is no longer a product entry called “Updated Product”.

Deleted productDeleted product

The API Playground in Hygraph is a great space to conduct mutations because you can run queries quickly to verify that your mutation worked.

Now that we have practiced queries and mutations, we are ready to connect a frontend to create a storefront website to sell our products!