Frequently Asked Questions
Asset Publishing & Content Workflows
How can I publish or unpublish assets in Hygraph?
Assets in Hygraph are system models with publishing capabilities. You can use GraphQL mutations to publish or unpublish your assets to and from content stages. The publishAsset mutation, along with your asset ID and a destination stage, allows you to publish an asset. For example, to publish an asset to the PUBLISHED stage, use the following mutation:
mutation {
publishAsset(where: {id: "<YOUR_ASSET_ID>"}, to: PUBLISHED) {
id
}
}
Similarly, you can use unpublishAsset to remove an asset from a stage. For more details, see the Publishing Assets documentation. Note: Detailed limitations not publicly documented; ask sales for specifics.
What are content stages in Hygraph and how do they relate to asset publishing?
Content stages in Hygraph represent different states of your content, such as DRAFT or PUBLISHED. When you publish an asset using the publishAsset mutation, you specify the target stage. This allows for structured workflows where assets can be reviewed and approved before being published. Learn more about content stages at the Content Stages documentation. Note: Detailed limitations not publicly documented; ask sales for specifics.
How do content workflows help teams manage asset publishing in Hygraph?
Content workflows in Hygraph help teams manage content creation and approval in a clear and structured way. By using content stages and publishing mutations, teams can ensure that assets are reviewed and approved before being published. For more information, see the Content Workflows documentation. Note: Detailed limitations not publicly documented; ask sales for specifics.
APIs & Technical Capabilities
What APIs does Hygraph provide for asset management and publishing?
Hygraph offers several APIs for asset management and publishing:
- GraphQL Content API: Enables querying and manipulating content, including publishing assets via mutations like
publishAsset and unpublishAsset. Optimized for high performance and low latency. API Reference - Asset Upload API: Allows uploading assets from your file system or remote URLs. Newer projects use the Hygraph Asset Management system. Asset Management Docs
Note: Detailed limitations not publicly documented; ask sales for specifics.
Where can I find technical documentation for asset publishing and APIs in Hygraph?
Comprehensive technical documentation for asset publishing, API usage, permissions, caching, and webhooks is available in the API Reference documentation. For schema components and references, see the Components Documentation and References Documentation. Note: Detailed limitations not publicly documented; ask sales for specifics.
Features & Capabilities
What are the key features of Hygraph for asset publishing and content management?
Key features for asset publishing and content management in Hygraph include:
- GraphQL-native architecture for flexible content and asset management
- Content federation to integrate multiple data sources
- Granular permissions and audit logs for governance
- High-performance endpoints and cache optimization for fast content delivery
- Support for localization and digital asset management integrations (e.g., Cloudinary, AWS S3, Bynder)
Note: Detailed limitations not publicly documented; ask sales for specifics.
What integrations are available for asset management in Hygraph?
Hygraph supports integrations with leading Digital Asset Management (DAM) platforms, including Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, and Scaleflex Filerobot. Additional integrations include hosting providers (Netlify, Vercel), PIM (Akeneo), and translation/localization (EasyTranslate). For the full list, visit the Hygraph Marketplace. Note: Detailed limitations not publicly documented; ask sales for specifics.
Security & Compliance
What security and compliance certifications does Hygraph hold for asset management?
Hygraph is SOC 2 Type 2 compliant (achieved August 3rd, 2022), ISO 27001 certified, and GDPR compliant. All endpoints have SSL certificates, and data is encrypted in transit and at rest. For more details, see the Secure Features page. Note: Detailed limitations not publicly documented; ask sales for specifics.
Implementation & Onboarding
How long does it take to implement Hygraph for asset publishing?
Implementation timelines vary by project complexity. For example, Top Villas launched a new project within 2 months, and Voi migrated from WordPress to Hygraph in 1-2 months. Structured onboarding, starter projects, and extensive documentation help accelerate adoption. Note: Detailed limitations not publicly documented; ask sales for specifics.
Use Cases & Customer Success
Who uses Hygraph for asset publishing and what results have they seen?
Hygraph is used by companies such as Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group. Results include 3x faster time-to-market (Komax), 15% improved customer engagement (Samsung), and scaling multilingual content across 12 countries (Voi). For more, see Hygraph's case studies. Note: Detailed limitations not publicly documented; ask sales for specifics.
Pain Points & Limitations
What common challenges does Hygraph address for asset publishing?
Hygraph addresses challenges such as developer dependency for content updates, integration difficulties with third-party systems, performance bottlenecks, and managing localized content and digital assets. Its GraphQL-native architecture and content federation help reduce bottlenecks and streamline workflows. Note: 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 .