19 篇文档带有标签「Document Service API」

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

In Strapi 5, core service methods use the Document Service API instead of the Entity Service API.

In Strapi 5, database lifecycle hooks are triggered differently with the various Document Service API methods.

The Document Service API is the recommended way to interact with your content from the back-end server or from plugins.

Documents should be called by their documentId in Content API calls (REST API & GraphQL).

Learn what a Document is in Strapi v5

In Strapi 5, the Entity Service API is deprecated in favor of the new Document Service API.

Learn how to transition from the Entity Service API of Strapi v4 to the Document Service API in Strapi 5

In Strapi 5, the Entity Service API is deprecated, and for the findPage() method you should use the Document Service API's findMany() method instead.

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.

Use Strapi's Document Service API to return either the draft or the published version of a document

Use Strapi's Document Service API to select the fields to return with your queries.

This document provides information about the filters available in the Document Service API.

Use Strapi's Document Service API to populate or select some fields.

Use Strapi's Document Service API to sort and paginate query results

Use Strapi's Document Service API to work with locale versions with your queries.

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