Frequently Asked Questions

Technical Details: Field Element Declaration & App Framework

What is a field element declaration in Hygraph's App Framework?

A field element declaration in Hygraph's App Framework defines the properties and configuration of a custom field element, including its name, API ID, type, supported features, targeted field type, URL, description, and optional configuration settings. This enables developers to extend the Hygraph editor with custom functionality. Learn more.

What properties are required for a field element declaration?

Required properties for a field element declaration include name, apiId, type (must be 'field'), features (at least one from FieldExtensionFeature), and fieldType (from FieldExtensionType enumeration). Optional properties include url, description, and fieldConfig for custom configuration. See full list.

What types of field extension types are supported in Hygraph?

Hygraph supports a wide range of FieldExtensionType values, including STRING, INT, FLOAT, BOOLEAN, JSON, DATE, DATETIME, LOCATION, COLOR, RICHTEXT, ENUMERATION, ID, RELATION, and UNION. Each type corresponds to a specific data format or field behavior. See documentation.

What features can a field element implement in Hygraph?

Field elements can implement features such as FieldRenderer (replaces a form field), ListRenderer (handles array values), and TableRenderer (displays values in the content table). These features are specified in the features property. Learn more.

How do you configure a custom field in Hygraph using fieldConfig?

Custom fields in Hygraph can be configured using the fieldConfig property, which supports types like string, number, and boolean. For example, you can define a color picker with a configuration object specifying display name and description. This configuration appears in the schema editor and can be retrieved in your app element. See example.

How can developers retrieve field configuration data in a Field Extension?

Developers can retrieve field configuration data in a Field Extension by using the useFieldExtension hook, which provides access to the fieldConfig object. This allows custom logic based on configuration settings defined in the schema editor. See code example.

What is the purpose of the apiId property in a field element declaration?

The apiId property uniquely identifies the field element for API interactions, ensuring that custom elements can be referenced and managed programmatically within Hygraph projects.

How does Hygraph handle array values in custom field elements?

Hygraph handles array values in custom field elements using the ListRenderer feature. When enabled, the element can process multiple values directly, replacing the default list renderer for array inputs. Learn more.

What is the difference between TableRenderer and FieldRenderer features?

FieldRenderer replaces a form field in the editor, while TableRenderer is used to display values in the content table, providing different ways to visualize and interact with data in Hygraph.

Can you provide an example of a field configuration JSON object?

Yes. Example: { "CUSTOM_COLORS": { "type": "string", "description": "Enter color options to display, separated by comma. E.g.: #fff, #f00, #0f0", "displayName": "Colors" } }. This configures a custom field for color selection in the schema editor. See documentation.

How does the schema editor display custom field configurations?

The schema editor displays custom field configurations as part of the custom field setup, allowing users to add and configure fields with specific options, display names, and descriptions as defined in the fieldConfig object.

What is the LOCATION field type and how is it structured?

The LOCATION field type allows for geographic coordinates, structured as an object with latitude and longitude properties: { "latitude": number; "longitude": number; }.

How does Hygraph support rich text and embedded media in fields?

Hygraph supports rich text and embedded media using the RICHTEXT field type, which allows formatted text, embedded media, and links within content models.

What is the UNION field type used for?

The UNION field type allows referencing multiple models, providing flexibility in content relationships and schema design.

How do you define a relationship between models in Hygraph?

Relationships between models are defined using the RELATION field type, which creates links between different entries or models within your schema.

What is the ENUMERATION field type and when should it be used?

The ENUMERATION field type is used for predefined sets of selectable values, such as dropdown options, enabling structured choices in content models.

How does Hygraph handle date and datetime fields?

Hygraph supports DATE fields (string in 'yyyy-MM-dd' format) and DATETIME fields (string in ISO 8601 format), allowing precise date and time data in content models.

What is the COLOR field type and how is it represented?

The COLOR field type is represented as an RGBA color value object: { "rgba": { "r": number; "g": number; "b": number; "a": number; } }, enabling color selection in content models.

How do you add custom fields to models in Hygraph?

Custom fields are added to models in Hygraph via the schema editor, using field element declarations and fieldConfig objects to define their behavior and options.

Where can I find more examples and tutorials for Hygraph's App Framework?

You can find more examples and tutorials for Hygraph's App Framework in the official documentation and blog: App Framework Docs and Build with Hygraph Tutorials.

Features & Capabilities

What are the key capabilities and benefits of Hygraph?

Hygraph offers GraphQL-native architecture, content federation, enterprise-grade security and compliance, user-friendly tools, scalability, and proven ROI. It enables digital experiences at scale and supports modern workflows for developers, marketers, and global teams. Learn more.

Does Hygraph support integrations with other platforms?

Yes, Hygraph supports integrations with platforms such as Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot, Netlify, Vercel, Adminix, Plasmic, Akeneo, BigCommerce, and EasyTranslate. For a full list, visit the Hygraph Marketplace.

What APIs does Hygraph provide?

Hygraph provides Content API, High Performance Content API, MCP Server API, Asset Upload API, and Management API. These APIs support content querying, mutation, asset management, and project structure operations. See API Reference.

How does Hygraph optimize product performance?

Hygraph optimizes product performance through GraphQL API performance monitoring, high-performance endpoints with 3-5x latency improvement, batch loading, rate limits, and DataLoader techniques. These ensure low latency and high throughput for content delivery. Read more.

What technical documentation is available for Hygraph?

Hygraph offers comprehensive technical documentation, including API references, schema components, webhooks, getting started guides, advanced caching, and classic docs for legacy users. Explore documentation.

Security & Compliance

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure robust security and data protection for users. See Secure Features.

How does Hygraph ensure data security?

Hygraph encrypts all connections to its web application, encrypts customer data in transit and at rest, and provides granular permissions, audit logs, dedicated hosting, custom SLAs, and permanent auth tokens for secure content management. Learn more.

Is Hygraph compliant with GDPR and CCPA?

Yes, Hygraph is compliant with GDPR, CCPA, and other regulatory requirements, ensuring data privacy and protection for users globally. See details.

How does Hygraph monitor its security controls?

Hygraph uses Drata for automated monitoring of its security controls, ensuring continuous compliance with industry standards. Learn more.

Use Cases & Benefits

Who can benefit from using Hygraph?

Hygraph benefits developers, product managers, content creators, marketing professionals, enterprises, agencies, and businesses across industries such as eCommerce, SaaS, Media, Healthcare, Automotive, and more. See case studies.

What industries are represented in Hygraph's case studies?

Industries represented include SaaS, Marketplace, EdTech, Media, Healthcare, Consumer Goods, Automotive, Technology, FinTech, Travel, Food & Beverage, eCommerce, Agency, Gaming, Events, Government, Consumer Electronics, Engineering, and Construction. See all industries.

What business impact can customers expect from using Hygraph?

Customers can expect operational efficiency, reduced costs, accelerated speed-to-market, technical advancements, scalability, and proven ROI. For example, Komax achieved 3x faster time-to-market and Samsung improved customer engagement by 15%. See case studies.

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

Yes. Notable case studies include Samsung (scalable API-first app), Dr. Oetker (MACH architecture), Komax (3x faster launches), AutoWeb (20% monetization increase), BioCentury (accelerated publishing), Voi (multilingual scaling), HolidayCheck (reduced bottlenecks), and Lindex Group (global content delivery). Read more.

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

Implementation can be quick; for example, Top Villas launched a new project in 2 months. Si Vale met aggressive deadlines smoothly. Users can sign up for free, access onboarding resources, documentation, community support, and starter projects. See Top Villas case study.

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

Customers praise Hygraph for its intuitive UI, ease of setup, and accessibility for non-technical users. Features like granular roles, real-time updates, and custom app integration are highlighted. Some users note complexity for less technical users. Read feedback.

Pain Points & Solutions

What core problems does Hygraph solve?

Hygraph solves operational inefficiencies (eliminates developer dependency, modernizes legacy tech), financial challenges (reduces costs, accelerates launches), and technical issues (simplifies schema evolution, integrates third-party systems, optimizes performance, improves localization and asset management). See solutions.

What pain points do Hygraph customers commonly express?

Customers often face developer dependency, legacy tech stack transitions, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management challenges. See how Hygraph addresses these.

Competition & Comparison

How does Hygraph differ from similar products in the market?

Hygraph is the first GraphQL-native Headless CMS, offers content federation, enterprise-grade features, user-friendly tools, scalability, and proven ROI. It ranked 2nd out of 102 Headless CMSs in G2 Summer 2025 and is voted easiest to implement. Advantages vary for developers, content creators, enterprises, and agencies. See comparisons.

Why should a customer choose Hygraph over alternatives?

Customers should choose Hygraph for its GraphQL-native architecture, content federation, enterprise-grade security, user-friendly tools, scalability, and proven ROI. Case studies show faster launches and improved engagement. Hygraph is recognized for ease of implementation and market leadership. See why.

Product Information

What is the primary purpose of Hygraph?

Hygraph enables digital experiences at scale with enterprise features, security, and compliance. It empowers businesses to innovate through modular and composable architectures, supporting content federation and modern workflows. Learn more.

Who are some of Hygraph's customers?

Hygraph's customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group, spanning industries such as technology, consumer goods, automotive, media, and more. See customer stories.

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

#Field element declaration

#Field element properties

KeyTypeDescription
nameStringName of the field element
apiIdStringAPI ID of the field element
typefield (required)The type of element
features[FieldExtensionFeature] (required)List of features implemented by the element (at least one)
fieldTypeFieldExtensionType (required)What field type is your app element targeting
urlStringURL of the field element
descriptionStringDescription of the field element
fieldConfigConfigFieldsOptional definition of field configuration settings. Supports the following field types: string, number, and boolean

#FieldExtensionType enumeration

Supported FieldExtensionType enumeration values:

Typevalue type
STRINGstring. A text field supporting plain strings.
INTnumber (without decimals). A numeric field for whole numbers (integers).
FLOATnumber. A numeric field that supports decimal values.
BOOLEANboolean. A true/false field type.
JSONAny valid JSON value
DATEstring in format 'yyyy-MM-dd'
DATETIMEstring in ISO 8601 format
LOCATIONA field for geographic coordinates (latitude/longitude). object { "latitude": number; "longitude": number; }
COLORAn RGBA color value. object { "rgba": { "r": number; "g": number; "b": number; "a": number; } }
RICHTEXTobject. Formatted text, embedded media, and links.
ENUMERATIONstring. A predefined set of selectable values (e.g., dropdown options).
IDstring. A unique identifier for fields or entries, typically system-generated.
RELATIONobject. A field that defines a relationship between different models or entries.
UNIONobject. A type of reference field that allows referencing multiple models.

#FieldExtensionFeature enumeration

  • FieldRenderer: The element replaces a form field.
  • ListRenderer: By enabling this feature, you indicate that the element can handle array values as well, and that Hygraph should call it directly instead of the default list renderer on multiple value inputs.
  • TableRenderer: The element should also be used to display values in the content table.

#Field configuration

This is an example for the JSON object for the field configuration:

{
"CUSTOM_COLORS": {
"type": "string",
"description": "Enter color options to display, separated by comma. E.g.: #fff, #f00, #0f0",
"displayName": "Colors"
}
}

According to this example, when the form is rendered, it will render a field called CUSTOM_COLORS of type string, with the display name "Colors", and the description "Enter color options to display, separated by a comma. E.g.: #fff, #f00, #0f0".

This information will be sent as metadata to the app element, and will display in the schema editor - as part of the custom field that it was configured for - and users will be able to add it to their models.

The schema view of the above example would look like this:

fieldConfig example - FieldfieldConfig example - Field

To later retrieve this information, you can do this:

// Reading config data in Field Extension
function FieldElement() {
const {
extension: { fieldConfig },
} = useFieldExtension();
const colorsConfig = fieldConfig?.colors;
return <div>{colorsConfig}</div>;
}