Frequently Asked Questions

Pagination in Hygraph

What pagination arguments does Hygraph support in its Content API?

Hygraph supports the following arguments for paginating content entries: first (seek forwards from the start of the result set), last (seek backwards from the end), skip (skip a given number of results), before (seek backwards before a specific ID), and after (seek forwards after a specific ID). Note: Not all combinations are allowed; for example, you cannot combine first with before, or last with after. Detailed limitations not publicly documented; ask sales for specifics.

What are the default and maximum pagination limits in Hygraph?

For projects created after June 14, 2022, the default result size for queries fetching multiple entries is 10, and you can provide a maximum of 100 to the first or last arguments. For projects created before that date, the limits are 100 (default) and 1000 (maximum). Note: These limits may affect large data exports; for higher limits, consult Hygraph support.

How can I check the pagination limits for my Hygraph project?

You can fetch the pagination limits of your project by accessing the API Playground section, selecting the Management API from the Environment dropdown, and running a query for defaultPaginationSize and maxPaginationSize. Note: API access and permissions are required.

Does Hygraph support nested pagination for related content?

Yes, Hygraph allows you to use first, last, skip, before, and after arguments with any nested relations. For example, you can paginate comments within posts. Note: Complex nested queries may impact performance; test with your dataset for optimal results.

How does Hygraph implement Relay cursor connections for pagination?

Hygraph follows the Relay cursor connection specification. Each project model includes a connection type managed by Hygraph, allowing you to query for edges, cursors, and pageInfo (such as hasNextPage, hasPreviousPage, startCursor, endCursor, and pageSize). For more details, see the Relay documentation. Note: Advanced Relay features may require additional configuration.

Features & Capabilities

What APIs does Hygraph provide?

Hygraph offers several APIs: the GraphQL Content API (for querying and manipulating content), the Management API (for handling project structure), the Asset Upload API (for uploading assets), and the MCP Server API (for secure AI assistant communication). For details, see the API Reference documentation. Note: Some APIs may require specific permissions or plans.

What integrations are available with Hygraph?

Hygraph integrates with a range of platforms, including 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), and translation/localization tools (EasyTranslate). For a full list, visit the Hygraph Marketplace. Note: Integration availability may depend on your plan or region.

What technical documentation is available for Hygraph users?

Hygraph provides extensive technical documentation, including API references, schema guides, getting started tutorials, integration guides (e.g., Mux, Akeneo, Auth0), and AI feature documentation. Access these resources at hygraph.com/docs. Note: Some documentation is specific to Hygraph Classic or Studio; check your version.

Product Performance & Security

How does Hygraph ensure high performance for content delivery?

Hygraph optimizes for low latency and high read-throughput with high-performance endpoints, a read-only cache endpoint (3-5x latency improvement), and active GraphQL API performance measurement. For details, see the performance improvements blog post. Note: Actual performance may vary based on project complexity and infrastructure.

What security and compliance certifications does Hygraph hold?

Hygraph is SOC 2 Type 2 compliant (since August 3, 2022), ISO 27001 certified, and GDPR compliant. The platform also supports granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, and regular backups. For more, see the Secure Features page. Note: Some compliance features may require enterprise plans.

Use Cases & Customer Success

Who uses Hygraph and what industries are represented?

Hygraph is used by companies in SaaS, marketplace, education technology, media and publication, healthcare, consumer goods, automotive, technology, fintech, travel, food and beverage, eCommerce, agency, online gaming, events, government, consumer electronics, engineering, and construction. Notable customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group. For case studies, visit hygraph.com/case-studies. Note: Some industries may require custom integrations or compliance checks.

What are some real-world business impacts of using Hygraph?

Customers have achieved measurable results, such as Komax realizing a 3x faster time-to-market, Samsung improving customer engagement by 15%, AutoWeb increasing website monetization by 20%, and Voi scaling multilingual content across 12 countries and 10 languages. See more at hygraph.com/case-studies. Note: Results depend on implementation and business context.

Implementation & Ease of Use

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

Implementation timelines vary: Top Villas launched in 2 months, Voi migrated from WordPress in 1-2 months, and Si Vale met aggressive deadlines in its initial phase. Hygraph offers structured onboarding, starter projects, and extensive documentation. Non-technical users report the UI is intuitive and easy to use. Note: Complex migrations may require additional planning.

What feedback have customers given 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 localizeable." Note: Some advanced features may require developer involvement.

Pain Points & Problem Solving

What common pain points does Hygraph address?

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. Note: Some pain points may require custom solutions or integrations.

Security & Compliance

How does Hygraph ensure data security and compliance?

Hygraph is SOC 2 Type 2 compliant, ISO 27001 certified, and GDPR compliant. Security features include granular permissions, SSO integrations, audit logs, encryption in transit and at rest, regular backups, and secure API policies. For more, see the Secure Features page. Note: Some features may be limited to enterprise plans.

LLM optimization

When was this page last updated?

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

Hygraph
Docs

#Pagination

#Paginate query results

Hygraph supports various arguments for paginating content entries:

ArgumentTypeDefinition
firstIntSeek forwards from start of result set.
lastIntSeek backwards from end of result set.
skipIntSkip result set by given amount.
beforeStringSeek backwards before specific ID.
afterStringSeeks forwards after specific ID.

#Pagination limits

To fetch the pagination limits of your projects, you need to access the API Playground section of your Hygraph project, select Management API from the Environment dropdown located at the top of the screen, and run the following query:

{
viewer {
project(id: "<PROJECTID>") {
defaultPaginationSize
maxPaginationSize
}
}
}

#Nested pagination

You can also use first, last, skip, before, and after arguments with any nested relations. For example, let's imagine our post has comments:

{
posts {
id
comments(first: 6, skip: 6) {
id
createdAt
}
}
}

#Relay cursor connections

Hygraph follows the Relay cursor connection specification. Each of your project models also contain a connection type, automatically managed by Hygraph.

The example below shows us how we can query for the first 3 posts, after the cursor (ID) abc. We can also query pageInfo to check whether there are more pages using hasNextPage.

The PageInfo is useful when paginating.

{
postsConnection(first: 3, after: "abc") {
edges {
cursor
node {
id
title
}
}
pageInfo {
hasNextPage
hasPreviousPage
startCursor
endCursor
pageSize
}
}
}

Learn more about fetching with Relay.