Frequently Asked Questions

Remote Sources Configuration

What types of remote sources can I add in Hygraph?

Hygraph allows you to add three types of remote sources: Custom, CommerceTools, and CommerceLayer. You can select the type when adding a remote source in the Schema Builder. Note: Only these three types are supported as pre-built options; for other integrations, custom configuration is required.

How do I add a remote source in Hygraph?

To add a remote source, navigate to the Schema Builder, find the Remote Sources section, and click +Add. Select the remote source type (Custom, CommerceTools, or CommerceLayer), then complete the required fields such as Display Name, Prefix, Description, and Type (REST or GraphQL). For OAuth-based sources like CommerceTools and CommerceLayer, you must also provide authorization details. For step-by-step instructions, see the official documentation. Note: Only the listed types are supported; other APIs require custom configuration.

What fields are required to configure a custom remote source?

When configuring a custom remote source, you must provide a Display Name, Prefix (auto-generated), optional Description, enable or disable debugging, and select the Type (REST or GraphQL). Additional fields will appear based on your selection. For REST or GraphQL, you must specify the Base URL, and can optionally add Headers and Custom Type Definitions. Note: Debugging should be disabled after setup to avoid leaking sensitive data.

How do I configure a CommerceTools remote source in Hygraph?

To configure a CommerceTools remote source, you need to provide OAuth credentials (Authorization URL, Scopes, Client ID, Client Secret) and then configure the remote source details (Display Name, Prefix, Description, Debugging, Type). The Authorization URL should be in the format https://<YOUR_BASE_ENDPOINT>/oauth/token. For more details, see the CommerceTools example. Note: You must have valid CommerceTools credentials to complete this setup.

How do I configure a CommerceLayer remote source in Hygraph?

To configure a CommerceLayer remote source, provide the OAuth Authorization URL, optional Scopes, Client ID, and optionally Client Secret. Then, complete the remote source details (Display Name, Prefix, Description, Debugging, Type). The Authorization URL should be https://<YOUR_BASE_ENDPOINT>/oauth/token. For a full example, see the CommerceLayer example. Note: Some fields are optional, but valid credentials are required for successful integration.

What is the difference between REST and GraphQL remote sources in Hygraph?

When configuring a remote source, you can choose between REST and GraphQL types. For REST, you must provide a Base URL, optional Headers, and can define custom type definitions to map API responses to the GraphQL schema. For GraphQL, you provide a Base URL, optional Headers, and can specify introspection details (method, URL, headers). REST sources require custom type definitions to translate REST responses into GraphQL types. Note: The choice depends on the API you are integrating; not all APIs support both types.

How do I create custom type definitions for remote sources?

To create custom type definitions, use the GraphQL Schema Definition Language (SDL) to specify the shape of the API response. You can use tools like the JSON to SDL converter to generate SDL from a JSON response. Add the SDL in the Custom Type Definitions section when configuring your remote source. Nested types are supported. For more details, see the official guide. Note: You may need to adjust the generated SDL for compatibility.

Can I pass input parameters to remote source endpoints in Hygraph?

Yes, you can define custom input type definitions using GraphQL SDL to pass input parameters to remote source endpoints. This is useful when the required data is not stored in Hygraph but provided at query time. For example, you can define an input type for a productId and use it in your queries. See the custom input type definition guide for details. Note: Input types must be defined using SDL and referenced in your queries.

Features & Capabilities

What integrations does Hygraph support?

Hygraph supports integrations with Digital Asset Management (DAM) 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: Some integrations may require additional configuration or credentials.

Does Hygraph provide APIs for content and asset management?

Yes, Hygraph provides several APIs: 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 communication with AI assistants. For details, see the API Reference documentation. Note: API usage may be subject to rate limits and permissions.

What technical documentation is available for Hygraph?

Hygraph offers extensive technical documentation, including API references, schema guides, getting started tutorials, integration guides (e.g., Mux, Akeneo, Auth0), and AI feature documentation. Access all resources at the Hygraph Documentation page. Note: Documentation is updated regularly; check for the latest guides relevant to your version.

Security & Compliance

What security and compliance certifications does Hygraph have?

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. For more details, visit the Secure Features page. Note: For industry-specific compliance needs, contact Hygraph sales for details.

What security features does Hygraph offer?

Hygraph provides granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups with one-click recovery, and secure API policies (custom origin policies, IP firewalls). All endpoints use SSL certificates. For more, see the Secure Features page. Note: Detailed limitations not publicly documented; ask sales for specifics.

Performance & Implementation

How does Hygraph perform for content delivery and API usage?

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 developers can find optimization advice in the GraphQL Report 2024. Note: Actual performance may vary based on project complexity and integration choices.

How long does it take to implement Hygraph?

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. Starter projects and structured onboarding are available to accelerate setup. Note: Large-scale or highly customized projects may require additional time.

Use Cases & Customer Success

Who can benefit from using Hygraph?

Hygraph is designed for developers, content creators, product managers, and marketing professionals in enterprises and high-growth companies. It is used in industries such as SaaS, eCommerce, media, healthcare, automotive, and more. For a full list of industries, see the case studies page. Note: Teams with highly specialized CMS needs may require custom solutions.

What business impact can customers expect from using Hygraph?

Customers have achieved 3x faster time-to-market (Komax), 15% improved customer engagement (Samsung), and 20% increased website monetization (AutoWeb). Hygraph supports consistent content delivery, cost reduction, and scalability. See more examples on the case studies page. Note: Results depend on implementation and organizational readiness.

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

Customers praise Hygraph's intuitive interface, quick adaptability, and accessibility for non-technical users. For example, Sigurður G. (CTO) noted the UI is intuitive, and Anastasija S. (Product Content Coordinator) highlighted instant front-end updates. See more feedback on the product page. Note: Some advanced features may require technical expertise.

Pain Points & Problem Solving

What problems does Hygraph solve for content teams?

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. These are solved through its GraphQL-native architecture, content federation, and user-friendly tools. Note: Some highly specialized requirements may need custom development.

Product Information & Differentiators

What makes Hygraph different from other CMS platforms?

Hygraph is the first GraphQL-native Headless CMS, supports content federation (integrating multiple data sources without duplication), and offers enterprise-grade features (security, compliance, Smart Edge Cache, localization). It ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report and was voted easiest to implement four times. Note: Teams requiring a traditional monolithic CMS may prefer other solutions.

What are some notable customer success stories with Hygraph?

Notable customers include Samsung (15% improved engagement), Komax (3x faster time-to-market), AutoWeb (20% increased monetization), Dr. Oetker, BioCentury, Voi, HolidayCheck, and Lindex Group. See all case studies at the case studies page. Note: Outcomes depend on project scope and execution.

LLM optimization

When was this page last updated?

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

Hygraph
Docs

#Remote Source configuration

#Add a remote source

Remote Sources - Select a typeRemote Sources - Select a type

The first step to adding a remote source to your project is selecting the type. You can create a custom source or use a pre-built one. Hygraph offers pre-built remote sources for CommerceTools and CommerceLayer.

  1. Navigate to the Schema Builder.
  2. In the left sidebar, find the Remote Sources section at the bottom of the list, then click +Add.
  3. Use the selection boxes at the top of the screen to select a remote source type:
    • Custom
    • CommerceTools
    • CommerceLayer

#Add a custom source

Add custom Remote Source

After selecting a custom remote source, you can complete the following fields:

FieldInput
Display NameEnter a display name here. This name will appear in Hygraph.
PrefixThe prefix is auto-generated and will be added to all types that are created for this Remote Source to avoid name clashes.
DescriptionYou can optionally add a description of the Remote Source here.
Enable debugging checkboxYou can enable debugging for this Remote Source, which will provide more information in case of errors. Make sure to disable this once you finish setting up the Remote Source to avoid leaking sensitive data.
TypeUse the radio buttons to set the type to either REST or GraphQL, depending on the type of API that this remote source will connect to. More fields will display as a result of your selection. Check out this document's “Select a type” section to learn more about configuring REST and GraphQL types.

#Add a commercetools source

Add CommerceTools Remote Source

After selecting a CommerceTools Remote Source, you will find that the screen now contains two distinct sections for you to complete. The first section is the OAuth configuration for CommerceTools:

FieldInput
Authorization URLEnter your CommerceTools authorization URL here. Copy the Base endpoint in your CommerceTools credentials screen, paste it in Hygraph, and add /oauth/token at the end, like this: https://<YOUR_BASE_ENDPOINT>/oauth/token.
ScopesProvide one or more scopes and click +Add. This is the Scope in the API client details view of your commercetools account. Click here to learn more about Commercetools scopes.
Client IDEnter your CommerceTools Client ID here. This is the client_id key in the API client details view of your commercetools account. Copy it and paste it in Hygraph. This is like a username.
Client SecretEnter your CommerceTools Client Secret here. This is the secret key in the API client details view of your commercetools account. Copy it and paste it in Hygraph. This is like a password.

Once you've completed this, you can move on to the second section, where you will configure the details of your Remote Source:

FieldInput
Display NameEnter a display name here. This name will appear in Hygraph.
PrefixThe prefix is auto-generated and will be added to all types that are created for this Remote Source to avoid name clashes.
DescriptionYou can optionally add a description of the remote source here.
Enable debugging checkboxYou can enable debugging for this remote source, which will provide more information in case of errors. Make sure to disable this once you finish setting up the Remote Source to avoid leaking sensitive data.
TypeUse the radio buttons to set the type to either REST or GraphQL, depending on the type of API that this remote source will connect to. More fields will display as a result of your selection. Check out this document's “Select a type” section to learn more about configuring REST and GraphQL types.

#Add a Commercelayer source

Add CommerceLayer Remote Source

After selecting a CommerceLayer remote source, you will find that the screen now contains two distinct sections for you to complete. The first section is the OAuth configuration for CommerceLayer:

FieldInput
Authorization URLEnter your CommerceLayer authorization URL here. Copy the Base endpoint in your Commercelayer credentials screen, paste it in Hygraph, and add /oauth/token at the end, like this: https://<YOUR_BASE_ENDPOINT>/oauth/token.
ScopesProvide one or more scopes and click +Add. This field is optional. Click here to learn more about Commercelayer scopes.
Client IDEnter your CommerceLayer Client ID here. Copy the Client ID in your Commercelayer credentials screen and paste it here.
Client SecretYou can optionally enter your CommerceLayer Client Secret here. This field is optional.

Once you've completed this, you can move on to the second section, where you will configure the details of your Remote Source:

FieldInput
Display NameEnter a display name here. This name will appear in Hygraph.
PrefixThe prefix is auto-generated and will be added to all types that are created for this Remote Source to avoid name clashes.
DescriptionYou can optionally add a description of the remote source here.
Enable debugging checkboxYou can enable debugging for this remote source, which will provide more information in case of errors. Make sure to disable this once you finish setting up the Remote Source to avoid leaking sensitive data.
TypeUse the radio buttons to set the type to either REST or GraphQL, depending on the type of API that this remote source will connect to. More fields will display as a result of your selection. Check out this document's “Select a type” section to learn more about configuring REST and GraphQL types.

#Select a type

#REST

Remote Source - REST

The following fields display when you select the REST type:

FieldInput
Base URLEnter a base URL here. All Remote Fields that connect to this Remote Source will use that base URL.
Commercetools Base URL: To form the base URL, you will use the API URL and the project_key from the API client details view of your commercetools account, like this: https://<COMMERCETOOLS_API_URL>/<PROJECT_KEY>/graphql.
Commercelayer Base URL: Copy the Base endpoint in your Commercelayer credentials screen and paste it here.
HeadersOptionally, you can include HTTP headers that will be added to all API requests for all Remote Fields connected to this Remote Source. Example use cases include authorization and accepted media types.
Custom type definitionsYou can now define your custom types here. These provide the mapping from the API responses to the GraphQL schema. Custom input types can optionally also be defined here.

#GraphQL

Remote Source - GraphQL

The following fields display when you select the GraphQL type:

FieldInput
Base URLEnter a base URL here. All Remote Fields that connect to this Remote Source will use that base URL.
Commercetools Base URL: To form the base URL, you will use the API URL and the project_key from the API client details view of your commercetools account, like this: https://<COMMERCETOOLS_API_URL>/<PROJECT_KEY>/graphql.
Commercelayer Base URL: Copy the Base endpoint in your Commercelayer credentials screen and paste it here.
HeadersOptionally, you can include HTTP headers that will be added to all API requests for all Remote Fields connected to this Remote Source. Example use cases include authorization and accepted media types.
Custom input type definitionYou can optionally provide an alternative introspection URL and custom headers to send to the introspection endpoint. If no separate introspection URL is provided, the base URL will be used (the default behavior for most GraphQL APIs is to allow querying and introspection on the same URL). Custom input types can optionally also be defined here.
Introspection methodSelect GET or POST.
If GET, we do a GET request and include the introspection query in the URL as a query parameter.
If POST, we do a POST request and include the introspection query in the body.
Introspection URLIf your introspection URL is different from the Remote Source URL, you can add it here.
Introspection headersHere, you can add the headers to pass along with the request to the remote source.
Simply add a key and value pair and click + Add header.

#Create a custom type definition

When connecting to a remote REST API, you will have the option to define a Custom Type Definition, which allows you to specify the shape of the response coming from the API. It will allow you to query the REST API as if it were native GraphQL.

These Custom Type Definitions use GraphQL SDL (Schema Definition Language).

Follow these steps to create a custom type definition:

  1. While adding a new Remote Source or editing an existing one, scroll down to Custom Type Definitions and click +Add.

  2. You can use our JSON to SDL converter tool to transform the JSON response from your API into valid GraphQL SDL. You might need to make a few tweaks to the generated SDL, especially changing the JSON type to Json (note the difference in casing).

    Here's an example of what that would look like:

  3. Add the SDL for your custom type to the input field. It's possible to add multiple types in a single input field, after saving the types will be moved to separate fields.

  4. Click Create or Save on the top right corner.

Custom types also support nesting, so they can make use of another type, as shown below:

type Product {
name: String
metaInfo: MetaInfo
slug: String
}
type MetaInfo {
createdAt: DateTime
createdBy: String
currency: String
}

In this example, the custom Product type makes use of another custom type MetaInfo.

#Create a custom input type definition

Remote Fields also allow you to pass along input parameters to your Remote Source endpoint. This can be useful if the identifiable information for the remote data isn't kept in Hygraph, but defined on a request basis. This is relevant for both the REST and GraphQL Remote Sources.

To create such a definition and to use it in a query, you will need to follow these steps:

  1. While adding a new Remote Source, or editing an existing one, scroll down to Custom Input Type Definition and click on +Add.

  2. Similar to the Custom Types, you need to use the GraphQL Schema Definition Language (SDL) to define what the input parameter will look like. A tool that could be used here is JSON2SDL, which allows translating a JSON object to a valid SDL. Keep in mind that we are not defining a type here, but an input.

    Let's take an example of passing a productId to our remote API, that will be used as an input argument. The SDL would look like this:

    input productInput {
    productId: String!
    }