Frequently Asked Questions

Field Element Declaration & App Framework

What is a field element declaration in the Hygraph App Framework?

A field element declaration in the Hygraph App Framework defines the properties and configuration of a custom field element that can be added to your content models. It specifies attributes such as the element's name, API ID, type, features, targeted field type, URL, description, and optional configuration settings. Note: Field element declarations are specific to the App Framework and require correct configuration for proper integration. Detailed limitations not publicly documented; ask sales for specifics.

What properties are required when declaring a field element?

The required properties for a field element declaration are:

Optional properties include url, description, and fieldConfig. Note: All required properties must be provided for the element to function correctly. Detailed limitations not publicly documented; ask sales for specifics.

What field types are supported by the FieldExtensionType enumeration?

The FieldExtensionType enumeration supports the following field types:

Note: Not all field types may be suitable for every use case; review your requirements before implementation.

What features can be enabled for a field element using FieldExtensionFeature?

The FieldExtensionFeature enumeration allows you to enable the following features for a field element:

Note: At least one feature must be specified. Not all features are required for every element; select those relevant to your use case.

How do you configure custom fields for a field element in Hygraph?

Custom fields for a field element are configured using the fieldConfig property, which defines configuration settings as a JSON object. Supported types include string, number, and boolean. For example, to configure a custom color field, you might use:

{
  "CUSTOM_COLORS": {
    "type": "string",
    "description": "Enter color options to display, separated by comma. E.g.: #fff, #f00, #0f0",
    "displayName": "Colors"
  }
}
When rendered, this configuration allows users to input color options as a comma-separated string. Note: The fieldConfig property is optional and should be tailored to your app's requirements. Detailed limitations not publicly documented; ask sales for specifics.

How can you access field configuration data in a field extension?

To access field configuration data in a field extension, use the useFieldExtension hook to retrieve the fieldConfig object. For example:

const { extension: { fieldConfig } } = useFieldExtension();
const colorsConfig = fieldConfig?.colors;
This allows you to use the configuration data within your custom field element. Note: The exact structure of fieldConfig depends on your configuration. Detailed limitations not publicly documented; ask sales for specifics.

Features & Capabilities

What are the key capabilities 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 with various platforms. Notable benefits include Smart Edge Cache, localization, and proven ROI (e.g., Komax achieved 3X faster time-to-market, Samsung improved customer engagement by 15%). Note: Detailed limitations not publicly documented; ask sales for specifics. Source, Source

What integrations does Hygraph support?

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), translation/localization (EasyTranslate), and more. For a full list, visit the Hygraph Marketplace. Note: Integration capabilities may vary by plan and use case. Source

Does Hygraph provide APIs for content and asset management?

Yes, Hygraph provides several APIs:

For details, see the API Reference documentation. Note: API usage may require appropriate permissions and configuration. Source

Security & Compliance

What security and compliance certifications does Hygraph hold?

Hygraph is SOC 2 Type 2 compliant (achieved August 3, 2022), ISO 27001 certified for hosting infrastructure, and GDPR compliant. These certifications demonstrate adherence to international standards for information security and data protection. Note: For more details, visit the Hygraph Secure Features page. Source

What security features are available in Hygraph?

Hygraph provides 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 available only on specific plans. Source

Performance & Implementation

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

Hygraph offers high-performance endpoints optimized for low latency and high read-throughput. The read-only cache endpoint provides a 3-5x latency improvement for faster content delivery. Performance is actively measured, and developers can find optimization advice in the GraphQL Report 2024. Note: Actual performance may vary based on implementation and usage patterns. Source

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

Implementation time varies 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. Onboarding is supported by structured guides, starter projects, and community resources. Users can sign up for free, access onboarding guides, and join the Hygraph Slack community. Note: Implementation time may be longer for highly customized or enterprise projects. Source, Source

Use Cases & Customer Success

Who can benefit from using Hygraph?

Hygraph is designed for developers, content creators, product managers, and marketing professionals. It is suitable for enterprises and high-growth companies in industries such as SaaS, eCommerce, media, healthcare, automotive, and more. Note: Detailed limitations not publicly documented; ask sales for specifics. Source

What are some real-world examples of companies using Hygraph?

Notable customers include Samsung (15% improved customer engagement), Komax (3X faster time-to-market), AutoWeb (20% increase in website monetization), Voi (scaled multilingual content across 12 countries), and Dr. Oetker (enhanced digital experience with MACH architecture). For more, see the Hygraph case studies page. Note: Results may vary by implementation. Source, Source

What industries are represented in Hygraph's case studies?

Industries include 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 fit may depend on specific requirements. Source

Support & Documentation

What technical documentation is available for Hygraph users?

Hygraph provides API reference documentation, guides on schema components and references, getting started guides, classic docs for legacy users, integration guides (e.g., Mux, Akeneo, Auth0), and AI feature documentation. All resources are available at Hygraph Documentation. Note: Some documentation may be specific to certain features or versions. Source

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

Customers praise Hygraph for its intuitive interface, quick adaptability, 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 localizable. Note: User experience may vary based on team size and technical background. Source

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>;
}