What is Hygraph's GraphQL API and how does it work?

Hygraph's GraphQL API is a data query and manipulation interface that allows you to fetch, update, and manage content using GraphQL. It supports both queries and mutations, enabling you to retrieve single or multiple entries, manage relations, handle localizations, filter by content stage, and more. The API is automatically generated based on your content models and supports advanced features like batch mutations, upserts, and versioning. Note: While the API is highly flexible, complex queries may require careful schema design to avoid performance bottlenecks. Learn more in the API Reference documentation.

What field types are available in Hygraph's no-code GraphQL schema builder?

Hygraph's schema builder supports a wide range of field types, including String (single-line, multi-line, markdown, slug), Rich Text (returns raw, HTML, markdown, text), Integer, Float, Boolean, Date (ISO 8601), DateTime (ISO 8601), JSON, Asset (any file type), Color (HEX, RGBA, CSS), Location (latitude, longitude, distance), Enumeration (enums), Reference (simple and union), and Remote fields for external data. Note: Using JSON fields may reduce some GraphQL benefits, and assets cannot be deleted once created. See all field types in the documentation.

What are the main capabilities of Hygraph's GraphQL API?

Hygraph's GraphQL API allows you to fetch single or multiple entries, manage relations, handle localizations, filter by content stage, fetch versions, combine arguments and queries, use directives (@skip, @include), and leverage variables for dynamic queries. It also supports mutations for creating, updating, deleting, and upserting entries, as well as batch mutations and connecting related entries. Note: Some advanced features may require familiarity with GraphQL best practices. Read more in the API Reference.

Does Hygraph support content localization and versioning?

Yes, Hygraph supports content localization via its flexible localization API, allowing you to publish and fetch content in multiple locales. Versioning is also supported, enabling you to fetch data for a specific entry at a point in time using version queries. Note: Asset localization is supported, but assets cannot be deleted. Learn more about localization.

What filtering, ordering, and pagination options are available in Hygraph's API?

Hygraph provides filtering for all types added to models, which can be applied to single or multiple entries and nested object fields. Ordering is supported via the orderBy argument, and pagination can be managed using arguments like first, last, skip, before, and after. Note: Complex filters or large paginated queries may impact performance; test queries for optimal results. See filtering documentation.

What are the key features and benefits of using Hygraph?

Key features include a GraphQL-native architecture, content federation (integrating multiple data sources without duplication), enterprise-grade security and compliance (SOC 2 Type 2, ISO 27001, GDPR), Smart Edge Cache, localization, granular permissions, and a user-friendly interface for non-technical users. Hygraph also offers high-performance endpoints, extensive integrations, and structured onboarding. Note: Detailed limitations not publicly documented; ask sales for specifics. See secure features.

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 others like Adminix and Plasmic. For a full list, visit the Hygraph Marketplace. Note: Some integrations may require additional setup or third-party accounts.

How does Hygraph perform in terms of speed and reliability?

Hygraph is optimized for high performance, with low-latency, high read-throughput endpoints. The read-only cache endpoint delivers 3-5x latency improvement. Performance is actively measured and documented, with practical advice for developers available in the GraphQL Report 2024. Note: Actual performance may vary based on query complexity and infrastructure; test in your environment for best results.

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 compliant (since August 3, 2022), ISO 27001 certified, and GDPR compliant. It offers granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups, and secure API policies. Note: For highly regulated industries, confirm specific compliance needs with sales. See secure features.

Who is Hygraph designed for?

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, fintech, education, and more. Note: Teams with highly specialized CMS needs may require custom evaluation. See case studies.

What problems does Hygraph solve for its users?

Hygraph addresses operational inefficiencies (reducing developer dependency, modernizing legacy tech stacks, ensuring content consistency), financial challenges (lowering operational costs, accelerating speed-to-market, supporting scalability), and technical issues (simplifying schema evolution, integrating third-party systems, optimizing performance, and managing localization/assets). Note: Some legacy system migrations may require additional planning. See customer stories.

How long does it take to implement Hygraph?

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: Large-scale migrations may require additional time for planning and testing. See case study.

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 scaling multilingual content (Voi: 12 countries, 10 languages) and reduces developer bottlenecks (HolidayCheck). Note: Results may vary based on implementation and use case. See all case studies.

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

Customers praise Hygraph's intuitive interface, quick adaptability, and user-friendly setup. For example, Sigurður G. (CTO) noted the UI is intuitive for non-technical users, and Charissa K. (Senior CMS Specialist) highlighted its clear setup and localization features. Note: Some advanced features may require technical onboarding. See more feedback.

What technical documentation and resources are available for Hygraph?

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. Training resources include webinars, live streams, and community support via Slack. Note: Some advanced topics may require direct support or consultation. See all documentation.

Who are some notable customers using Hygraph?

Notable customers include Samsung (15% improved engagement), Dr. Oetker (MACH architecture), Komax (3x faster time-to-market), AutoWeb (20% increased monetization), BioCentury (accelerated publishing), Voi (multilingual scaling), HolidayCheck (reduced bottlenecks), and Lindex Group (global content delivery). See all case studies. Note: Results are specific to each customer’s implementation.

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. See all case studies. Note: Industry-specific requirements may affect implementation details.

When was this page last updated?

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

GraphQL API cheat sheet

Get started with building your own production ready GraphQL API within minutes using Hygraph. Here’s a cheatsheet to bring you up to speed!

What is GraphQL?

GraphQL is an open-source data query and manipulation language for APIs, and a runtime for fulfilling queries with existing data. Maintained and developed primarily via the GraphQL Foundation, GraphQL has had incredible adoption across a variety of verticals and use cases with organizations like Twitter, Facebook, Expedia, Shopify, and Hygraph to name a few.

3 Reasons we love GraphQL

Data Fetching: GraphQL gives you exactly what you ask for. No over or under fetching.

Schema & Type Safety: GraphQL uses a strongly typed system to define the capabilities of an API.

Content Federation: GraphQL can combine multiple APIs into a single schema to make it accessible to the client.

No-code GraphQL API schema builder field types in Hygraph

Embrace a low-code API management layer approach to unify your microservices and operations, and focus on growing your business model rather than maintaining it.

Learn about all the field types

String

A string is just a simple string field. Hygraph supports single-line text, multi-line text, markdown and slug, as string variants.

Rich Text

The Rich Text field is an advanced string field that returns your content in raw, html, markdown and text.

Integer

Integers are whole numbers, and are often used to reference price in cents, stock quantities etc.

Float

Floating point numbers represent fractional values with precision, such as distance, weight, volume, etc.

Boolean

Booleans are used for entries that should have a true or false value.

Date

The Date field type adheres to ISO 8601 standard. This means, October 7, 1989 is represented as 1989-10-07.

Date and Time

he DateTime field type also adheres to ISO 8601 standard, allowing you to set specific times on dates.

JSON

Often used for storing large amounts of data, this field could be seen as an “escape hatch” that could lose you some GraphQL benefits.

Asset

Assets are connected to models through a reference field. Assets can be any file type, not just images.

Color

The Color field stores values that can be retrieved in several formats like HEX, RGBA, and CSS color values.

Location

The Location field type returns latitude, longitude, and distance Float values.

Enumeration

Enums are a predefined list of values inside your GraphQL schema, and can be referenced by any content models.

Reference (Simple)

Relations allow you to connect multiple models. In Hygraph they come as one-way or two-way references.

Reference (Union)

GraphQL Union Types (or Polymorphic Relations) allow you to define a list of possible relations, and decide which one to use.

Remote

Remote fields allow you to programmatically bring external data into your graph, without copying them into the CMS.

Working with Hygraph’s GraphQL Query API

Hygraph automatically generates queries for fetching single, and multiple entries for each defined content type belonging to your project.

Learn more about working with our Queries API

Fetching Single Entries

The post query is what you would use to fetch a single entry from the CMS.

{
  post(where: { id: "..." }) {
    id
    title
  }
}

Fetching Multiple Entries

The posts query is what you would use to fetch multiple entries from the CMS.

{
  posts {
    id
  }
}

Fetching Relations

Imagine posts have a one to many relation with comments. With GraphQL you can query the related comments in the same request.

{
  posts {
    id
    comments {
      id
      author
    }
  }
}

Fetching Localizations

When fetching one or more entries, you can also fetch the localized entries. The default locale is set to en.

{
  post(where: { id: "..." }, locales: [en, fr, de]) {
    title
  }

  posts(locales: [en, fr, de]) {
    title
  }
}

Filtering on Stages

When fetching entries, you can also specify the content stage. The default content stage is set to DRAFT.

{
  post(where: { id: "..." }, stage: PUBLISHED) {
    title
  }

  posts(stage: PUBLISHED) {
    title
  }
}

Fetching Versions

You can fetch all data of a specific entry at a point in time using the automatically generated version query.

{
  postVersion(where: { id: "abc123", revision: 1, stage: PUBLISHED }) {
    id
    revision
    data
  }
}

Combining Arguments

It is also possible to pass multiple arguments at a time. Let’s get the first 3 published posts by time, where the title contains "Hygraph".

{
  posts(
    where: { title_contains: "Hygraph" }
    orderBy: createdAt_DESC
    first: 3
    stage: PUBLISHED
  ) {
    id
  }
}

Combining Queries

Multiple queries can be executed in parallel via a single request to your endpoint. Let's fetch our a single, and multiple posts in one request.

{
  post(where: { id: "..." }) {
    id
    title
  }

  posts {
    id
    title
  }
}

Directives

We support both the @skip and @include directives for use in your schema.

query ($includeAuthor: Boolean!) {
  posts {
    id
    title
    author @include(if: $includeAuthor) {
      name
    }
  }
}

Variables

It's recommended you use GraphQL variables when working with queries that use any variable data values.

query GetPostBySlug($slug: String!) {
  post(where: { id: $id }) {
    id
    title
  }
}

Working with the Hygraph’s GraphQL Mutations API

Your project endpoint exposes GraphQL mutations. The mutations API allows you to interact with content ouside of Hygraph using GraphQL.

Learn more about working with our Mutations API

Create Entries

When creating new content entries, the data argument will have an associated input type that is specific to your content model.

mutation {
  createProduct(
    data: {
      name: "Face Mask", 
      slug: "face-mask", 
      price: 1000 }
    ) {
    id
    name
    slug
    price
  }
}

Update Entries

When updating single content entry, you must specify the unique where criteria of which you want to update, as well as the new data.

mutation {
  updateProduct(
    where: { id: "ckgcd5hzc01wd0a446vd3kqrs" }
    data: { price: 100 }
  ) {
    id
    name
    price
  }
}

Batch Mutations

Hygraph supports batch mutations that can be applied to "many" entries at once. They comply with Relay connection type specification.

mutation {
  updateManyProductsConnection(
    where: { featured: true }
    data: { featured: false }
  ) {
    edges {
      node {
        featured
      }
    }
  }
}

Insert Mutations

When inserting related entries, you can connect entries at a given position. The position of entries reflects that fetching relations.

mutation {
  updateAuthor(
    where: { id: "..." }
    data: { posts: { connect: { position: { before: "..." } } } }
  ) {
    id
  }
}

Delete Entries

Similar to updating, and upserting entries, you can specify using where the entries you want to delete.

mutation {
  deleteProduct(where: { id: "..." }) {
    id
    name
    slug
    price
  }
}

Upsert Entries

The upsert mutation allows you to create, or update a content entry based on whether the unique where values exist.

mutation {
  upsertProduct(
    where: { slug: "face-mask" }
    upsert: {
      create: { name: "Face Mask", slug: "face-mask", price: 1000 }
      update: { name: "Face Mask", slug: "face-mask", price: 1000 }
    }
  ) {
    id
    name
    slug
    price
  }
}

Get started for free, or request a demo
to discuss larger projects

Contact sales Get started

GraphQL API cheat sheet

Get started with building your own production ready GraphQL API within minutes using Hygraph. Here’s a cheatsheet to bring you up to speed!

What is GraphQL?

3 Reasons we love GraphQL

Data Fetching: GraphQL gives you exactly what you ask for. No over or under fetching.

Schema & Type Safety: GraphQL uses a strongly typed system to define the capabilities of an API.

Content Federation: GraphQL can combine multiple APIs into a single schema to make it accessible to the client.

No-code GraphQL API schema builder field types in Hygraph

Embrace a low-code API management layer approach to unify your microservices and operations, and focus on growing your business model rather than maintaining it.

Learn about all the field types

String

A string is just a simple string field. Hygraph supports single-line text, multi-line text, markdown and slug, as string variants.

Rich Text

The Rich Text field is an advanced string field that returns your content in raw, html, markdown and text.

Integer

Integers are whole numbers, and are often used to reference price in cents, stock quantities etc.

Float

Floating point numbers represent fractional values with precision, such as distance, weight, volume, etc.

Boolean

Booleans are used for entries that should have a true or false value.

Date

The Date field type adheres to ISO 8601 standard. This means, October 7, 1989 is represented as 1989-10-07.

Date and Time

he DateTime field type also adheres to ISO 8601 standard, allowing you to set specific times on dates.

JSON

Often used for storing large amounts of data, this field could be seen as an “escape hatch” that could lose you some GraphQL benefits.

Asset

Assets are connected to models through a reference field. Assets can be any file type, not just images.

Color

The Color field stores values that can be retrieved in several formats like HEX, RGBA, and CSS color values.

Location

The Location field type returns latitude, longitude, and distance Float values.

Enumeration

Enums are a predefined list of values inside your GraphQL schema, and can be referenced by any content models.

Reference (Simple)

Relations allow you to connect multiple models. In Hygraph they come as one-way or two-way references.

Reference (Union)

GraphQL Union Types (or Polymorphic Relations) allow you to define a list of possible relations, and decide which one to use.

Remote

Remote fields allow you to programmatically bring external data into your graph, without copying them into the CMS.

Working with Hygraph’s GraphQL Query API

Hygraph automatically generates queries for fetching single, and multiple entries for each defined content type belonging to your project.

Learn more about working with our Queries API

Fetching Single Entries

The post query is what you would use to fetch a single entry from the CMS.

{
  post(where: { id: "..." }) {
    id
    title
  }
}

Fetching Multiple Entries

The posts query is what you would use to fetch multiple entries from the CMS.

{
  posts {
    id
  }
}

Fetching Relations

Imagine posts have a one to many relation with comments. With GraphQL you can query the related comments in the same request.

{
  posts {
    id
    comments {
      id
      author
    }
  }
}

Fetching Localizations

When fetching one or more entries, you can also fetch the localized entries. The default locale is set to en.

{
  post(where: { id: "..." }, locales: [en, fr, de]) {
    title
  }

  posts(locales: [en, fr, de]) {
    title
  }
}

Filtering on Stages

When fetching entries, you can also specify the content stage. The default content stage is set to DRAFT.

{
  post(where: { id: "..." }, stage: PUBLISHED) {
    title
  }

  posts(stage: PUBLISHED) {
    title
  }
}

Fetching Versions

You can fetch all data of a specific entry at a point in time using the automatically generated version query.

{
  postVersion(where: { id: "abc123", revision: 1, stage: PUBLISHED }) {
    id
    revision
    data
  }
}

Combining Arguments

It is also possible to pass multiple arguments at a time. Let’s get the first 3 published posts by time, where the title contains "Hygraph".

{
  posts(
    where: { title_contains: "Hygraph" }
    orderBy: createdAt_DESC
    first: 3
    stage: PUBLISHED
  ) {
    id
  }
}

Combining Queries

Multiple queries can be executed in parallel via a single request to your endpoint. Let's fetch our a single, and multiple posts in one request.

{
  post(where: { id: "..." }) {
    id
    title
  }

  posts {
    id
    title
  }
}

Directives

We support both the @skip and @include directives for use in your schema.

query ($includeAuthor: Boolean!) {
  posts {
    id
    title
    author @include(if: $includeAuthor) {
      name
    }
  }
}

Variables

It's recommended you use GraphQL variables when working with queries that use any variable data values.

query GetPostBySlug($slug: String!) {
  post(where: { id: $id }) {
    id
    title
  }
}

Working with the Hygraph’s GraphQL Mutations API

Your project endpoint exposes GraphQL mutations. The mutations API allows you to interact with content ouside of Hygraph using GraphQL.

Learn more about working with our Mutations API

Create Entries

When creating new content entries, the data argument will have an associated input type that is specific to your content model.

mutation {
  createProduct(
    data: {
      name: "Face Mask", 
      slug: "face-mask", 
      price: 1000 }
    ) {
    id
    name
    slug
    price
  }
}

Update Entries

When updating single content entry, you must specify the unique where criteria of which you want to update, as well as the new data.

mutation {
  updateProduct(
    where: { id: "ckgcd5hzc01wd0a446vd3kqrs" }
    data: { price: 100 }
  ) {
    id
    name
    price
  }
}

Batch Mutations

Hygraph supports batch mutations that can be applied to "many" entries at once. They comply with Relay connection type specification.

mutation {
  updateManyProductsConnection(
    where: { featured: true }
    data: { featured: false }
  ) {
    edges {
      node {
        featured
      }
    }
  }
}

Insert Mutations

When inserting related entries, you can connect entries at a given position. The position of entries reflects that fetching relations.

mutation {
  updateAuthor(
    where: { id: "..." }
    data: { posts: { connect: { position: { before: "..." } } } }
  ) {
    id
  }
}

Delete Entries

Similar to updating, and upserting entries, you can specify using where the entries you want to delete.

mutation {
  deleteProduct(where: { id: "..." }) {
    id
    name
    slug
    price
  }
}

Upsert Entries

The upsert mutation allows you to create, or update a content entry based on whether the unique where values exist.

mutation {
  upsertProduct(
    where: { slug: "face-mask" }
    upsert: {
      create: { name: "Face Mask", slug: "face-mask", price: 1000 }
      update: { name: "Face Mask", slug: "face-mask", price: 1000 }
    }
  ) {
    id
    name
    slug
    price
  }
}

Get started for free, or request a demo
to discuss larger projects

Contact sales Get started

GraphQL API cheat sheet

Get started with building your own production ready GraphQL API within minutes using Hygraph. Here’s a cheatsheet to bring you up to speed!

What is GraphQL?

3 Reasons we love GraphQL

Data Fetching: GraphQL gives you exactly what you ask for. No over or under fetching.

Schema & Type Safety: GraphQL uses a strongly typed system to define the capabilities of an API.

Content Federation: GraphQL can combine multiple APIs into a single schema to make it accessible to the client.

No-code GraphQL API schema builder field types in Hygraph

Embrace a low-code API management layer approach to unify your microservices and operations, and focus on growing your business model rather than maintaining it.

Learn about all the field types

String

A string is just a simple string field. Hygraph supports single-line text, multi-line text, markdown and slug, as string variants.

Rich Text

The Rich Text field is an advanced string field that returns your content in raw, html, markdown and text.

Integer

Integers are whole numbers, and are often used to reference price in cents, stock quantities etc.

Float

Floating point numbers represent fractional values with precision, such as distance, weight, volume, etc.

Boolean

Booleans are used for entries that should have a true or false value.

Date

The Date field type adheres to ISO 8601 standard. This means, October 7, 1989 is represented as 1989-10-07.

Date and Time

he DateTime field type also adheres to ISO 8601 standard, allowing you to set specific times on dates.

JSON

Often used for storing large amounts of data, this field could be seen as an “escape hatch” that could lose you some GraphQL benefits.

Asset

Assets are connected to models through a reference field. Assets can be any file type, not just images.

Color

The Color field stores values that can be retrieved in several formats like HEX, RGBA, and CSS color values.

Location

The Location field type returns latitude, longitude, and distance Float values.

Enumeration

Enums are a predefined list of values inside your GraphQL schema, and can be referenced by any content models.

Reference (Simple)

Relations allow you to connect multiple models. In Hygraph they come as one-way or two-way references.

Reference (Union)

GraphQL Union Types (or Polymorphic Relations) allow you to define a list of possible relations, and decide which one to use.

Remote

Remote fields allow you to programmatically bring external data into your graph, without copying them into the CMS.

Working with Hygraph’s GraphQL Query API

Hygraph automatically generates queries for fetching single, and multiple entries for each defined content type belonging to your project.

Learn more about working with our Queries API

Fetching Single Entries

The post query is what you would use to fetch a single entry from the CMS.

{
  post(where: { id: "..." }) {
    id
    title
  }
}

Fetching Multiple Entries

The posts query is what you would use to fetch multiple entries from the CMS.

{
  posts {
    id
  }
}

Fetching Relations

Imagine posts have a one to many relation with comments. With GraphQL you can query the related comments in the same request.

{
  posts {
    id
    comments {
      id
      author
    }
  }
}

Fetching Localizations

When fetching one or more entries, you can also fetch the localized entries. The default locale is set to en.

{
  post(where: { id: "..." }, locales: [en, fr, de]) {
    title
  }

  posts(locales: [en, fr, de]) {
    title
  }
}

Filtering on Stages

When fetching entries, you can also specify the content stage. The default content stage is set to DRAFT.

{
  post(where: { id: "..." }, stage: PUBLISHED) {
    title
  }

  posts(stage: PUBLISHED) {
    title
  }
}

Fetching Versions

You can fetch all data of a specific entry at a point in time using the automatically generated version query.

{
  postVersion(where: { id: "abc123", revision: 1, stage: PUBLISHED }) {
    id
    revision
    data
  }
}

Combining Arguments

It is also possible to pass multiple arguments at a time. Let’s get the first 3 published posts by time, where the title contains "Hygraph".

{
  posts(
    where: { title_contains: "Hygraph" }
    orderBy: createdAt_DESC
    first: 3
    stage: PUBLISHED
  ) {
    id
  }
}

Combining Queries

Multiple queries can be executed in parallel via a single request to your endpoint. Let's fetch our a single, and multiple posts in one request.

{
  post(where: { id: "..." }) {
    id
    title
  }

  posts {
    id
    title
  }
}

Directives

We support both the @skip and @include directives for use in your schema.

query ($includeAuthor: Boolean!) {
  posts {
    id
    title
    author @include(if: $includeAuthor) {
      name
    }
  }
}

Variables

It's recommended you use GraphQL variables when working with queries that use any variable data values.

query GetPostBySlug($slug: String!) {
  post(where: { id: $id }) {
    id
    title
  }
}

Working with the Hygraph’s GraphQL Mutations API

Your project endpoint exposes GraphQL mutations. The mutations API allows you to interact with content ouside of Hygraph using GraphQL.

Learn more about working with our Mutations API

Create Entries

When creating new content entries, the data argument will have an associated input type that is specific to your content model.

mutation {
  createProduct(
    data: {
      name: "Face Mask", 
      slug: "face-mask", 
      price: 1000 }
    ) {
    id
    name
    slug
    price
  }
}

Update Entries

When updating single content entry, you must specify the unique where criteria of which you want to update, as well as the new data.

mutation {
  updateProduct(
    where: { id: "ckgcd5hzc01wd0a446vd3kqrs" }
    data: { price: 100 }
  ) {
    id
    name
    price
  }
}

Batch Mutations

Hygraph supports batch mutations that can be applied to "many" entries at once. They comply with Relay connection type specification.

mutation {
  updateManyProductsConnection(
    where: { featured: true }
    data: { featured: false }
  ) {
    edges {
      node {
        featured
      }
    }
  }
}

Insert Mutations

When inserting related entries, you can connect entries at a given position. The position of entries reflects that fetching relations.

mutation {
  updateAuthor(
    where: { id: "..." }
    data: { posts: { connect: { position: { before: "..." } } } }
  ) {
    id
  }
}

Delete Entries

Similar to updating, and upserting entries, you can specify using where the entries you want to delete.

mutation {
  deleteProduct(where: { id: "..." }) {
    id
    name
    slug
    price
  }
}

Upsert Entries

The upsert mutation allows you to create, or update a content entry based on whether the unique where values exist.

mutation {
  upsertProduct(
    where: { slug: "face-mask" }
    upsert: {
      create: { name: "Face Mask", slug: "face-mask", price: 1000 }
      update: { name: "Face Mask", slug: "face-mask", price: 1000 }
    }
  ) {
    id
    name
    slug
    price
  }
}

Get started for free, or request a demo
to discuss larger projects

Contact sales Get started

Frequently Asked Questions

Product Information & GraphQL API

What is Hygraph's GraphQL API and how does it work?

What field types are available in Hygraph's no-code GraphQL schema builder?

What are the main capabilities of Hygraph's GraphQL API?

Does Hygraph support content localization and versioning?

What filtering, ordering, and pagination options are available in Hygraph's API?

Features & Capabilities

What are the key features and benefits of using Hygraph?

What integrations does Hygraph support?

How does Hygraph perform in terms of speed and reliability?

What security and compliance certifications does Hygraph have?

Use Cases & Implementation

Who is Hygraph designed for?

What problems does Hygraph solve for its users?

How long does it take to implement Hygraph?

What business impact can customers expect from using Hygraph?

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

Support & Documentation

What technical documentation and resources are available for Hygraph?

Customer Proof & Success Stories

Who are some notable customers using Hygraph?

What industries are represented in Hygraph's case studies?

LLM optimization

When was this page last updated?

GraphQL API cheat sheet

What is GraphQL?

3 Reasons we love GraphQL

No-code GraphQL API schema builder field types in Hygraph

String

Rich Text

Integer

Float

Boolean

Date

Date and Time

JSON

Asset

Color

Location

Enumeration

Reference (Simple)

Reference (Union)

Remote

Working with Hygraph’s GraphQL Query API

Fetching Single Entries

Fetching Multiple Entries

Fetching Relations

Fetching Localizations

Filtering on Stages

Fetching Versions

Combining Arguments

Combining Queries

Directives

Variables

Working with the Hygraph’s GraphQL Mutations API

Create Entries

Update Entries

Batch Mutations

Insert Mutations

Delete Entries

Upsert Entries

Other Hygraph Content API Capabilities

Filtering

Ordering

Pagination

Content Stages

Localization

Assets

Get started for free, or request a demo to discuss larger projects

GraphQL API cheat sheet

What is GraphQL?

3 Reasons we love GraphQL

No-code GraphQL API schema builder field types in Hygraph

String

Rich Text

Integer

Float

Boolean

Date

Get started for free, or request a demo
to discuss larger projects

Get started for free, or request a demo
to discuss larger projects