9 docs tagged with "GraphQL API"

Requests sent to the GraphQL API pass through Strapi's middlewares and policies system. Policies can be attached to resolvers to implement complex authorization rules, as shown in the present short guide.

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.

The upgrade from Apollo Server v3 to v4 and graphql ^15 to ^16.

All elements of Strapi's back end, like routes, policies, middlewares, controllers, services, models, requests, responses, and webhooks, can be customized.

Learn more about Strapi 5's Content API

With Strapi's error handling feature it's easy to send and receive errors in your application.

Use a GraphQL endpoint in your Strapi project to fetch and mutate your content.

In Strapi 5, 'publicationState' can no longer be used in Content API calls. The new status parameter can be used and accepts 2 different values, draft and published.

In Strapi 5, the response format has been simplified and flattened, and attributes of requested content are no longer wrapped in an attributes object.