11 docs tagged with "GraphQL API"

Policies can be attached to GraphQL resolvers to implement complex authorization rules, such as limiting results for unauthenticated users or restricting access based on group membership.

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.

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.

GraphQL queries and mutations for authentication, user management, and role-based access with the Users & Permissions feature.

Use the locale field and argument with Strapi's GraphQL API to query and mutate documents for a specific locale.