37 docs tagged with "Content API"

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

Use Strapi's Query Engine API to perform operations on multiple entries.

In Strapi 5, components and dynamic zones do not return an `id` with REST API requests so it's not possible to partially update them.

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

Use Strapi's Query Engine API to filter the results of your queries.

Use Strapi's REST API to filter the results of your requests.

The GraphQL API allows performing queries and mutations to interact with the content-types through Strapi's GraphQL plugin. Results can be filtered, sorted and paginated.

Learn how to populate creator fields such as createdBy and updatedBy by creating a custom controller that leverages the populate parameter.

Use an interactive tool that leverages the querystring library to build your query URL

In Strapi 5, it's no longer possible to get all localized versions with the '?locale=all' parameter.

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, the shared population strategy is not supported anymore, so components and dynamic zones must be explicitly populated using `on` fragments.

Use Strapi's Query Engine API to order and paginate the results of your queries.

Use API parameters to refine your Strapi REST API queries.

Use Strapi's REST API to populate or select certain fields.

Use Strapi's Query Engine API to populate relations when querying 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, '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.

Strapi provides a Query Engine API to give unrestricted internal access to the database layer at a lower level.

Use the REST API to manage the order of relations

In Strapi 5, some attributes and content types names are reserved, and all fields or content types using the reserved names should be renamed before migrating to prevent data loss.

Deep dive into some specific REST API topics using guides that extensively explain some use cases or give step-by-step instructions.

Interact with your Content-Types using the REST API endpoints Strapi generates for you.

Use Strapi's Query Engine API to perform operations on single entries.

Use Strapi's REST API to sort or paginate your data.

In Strapi 5, sorting by id is no longer possible to sort by chronological order, and you should use createdAt instead.

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

In Strapi 5, the GraphQL API has been updated. It handles the new, flattened response format, and can also now accept Relay-style queries.

Learn what populating means and how you can use the populate parameter in your REST API queries to add additional fields to your responses.

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.