Advanced queries for the GraphQL API#

Advanced queries in Strapi's GraphQL API use nested selection sets to fetch multi-level relations and custom resolver chains to reuse logic across resolvers and apply context-specific behavior.

Strapi's GraphQL API resolves many queries automatically, but complex data access can require deeper relation fetching or chaining resolvers. The present short guide explains how to handle such advanced scenarios.

For additional information, please refer to the GraphQL customization documentation.

Multi-level queries#

Use nested selection sets to fetch relations several levels deep, as in the following example:

{
  restaurants {
    documentId
    name
    categories {
      documentId
      name
      parent {
        documentId
        name
      }
    }
  }
}

The GraphQL plugin automatically resolves nested relations. If you need to apply custom logic at a specific level, create a custom resolver for that field.

Resolver chains#

Custom resolvers can call other resolvers to reuse existing logic. A common pattern is to resolve permissions or context data in a parent resolver and pass it down to child resolvers, as in the following example:

export default {
  Query: {
    restaurants: async (parent, args, ctx) => {
      const documents = await strapi.documents('api::restaurant.restaurant').findMany(args);
      return documents.map(doc => ctx.request.graphql.resolve('Restaurant', doc));
    },
  },
};

In this example the parent resolver fetches restaurants using the Document Service API, then delegates to the generated Restaurant resolver provided by the plugin so default behavior such as field selection still applies.

:::info Aggregations not yet available
GraphQL aggregations are not yet implemented in @strapi/plugin-graphql. See the GraphQL advanced use cases for details and workarounds.
:::