12 篇文档带有标签「GraphQL API」

* Administrators can create, read, update, or delete API tokens only if proper permissions are granted (see Configuring administrator roles).

Using API tokens allows executing a request on Strapi's REST API endpoints as an authenticated user.

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.

Instructions on how to use Strapi Content API with the Internationalization (i18n) optional plugin

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, 'publishedAt' can no longer be used in Content API calls to set the status. 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.

Strapi 5 brings many new features and improvements, and this page quickly highlights the most important documentation changes.