12 docs tagged with "content API"

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

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.

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

Draft & Publish is always enabled in Strapi v5 and this is reflected in the Content API models.

In Strapi 5, the 'locale' attribute name is reserved, and all custom fields also named 'locale' should be renamed before migrating to prevent data loss.

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, '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, 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.

In Strapi 5, the localizations field does not exist anymore, and queries should use the locale parameter instead. Not all Strapi v4 use cases might be directly achievable.