32 docs tagged with "Rest API"

Strapi's default API parameters can be configured.

* 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.

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

Controllers are JavaScript files that contain a set of methods, called actions, reached by the client according to the requested route. Whenever a client requests the route, the action performs the business logic code and sends back the response. Controllers represent the C in the model-view-controller (MVC) pattern.

Use Strapi's REST API to create and delete entries

Learn how to authenticate use custom services and controllers using our FoodAdvisor example

With Strapi's error handling feature it's easy to send and receive errors in your application.

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

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

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

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

The diagram represents a simplified version of how a request travels through the Strapi back end, with global middlewares highlighted. The backend customization introduction page includes a complete, interactive diagram.

Strapi models (i.e. content-types, components, and dynamic zones) define a representation of the data structure.

In Strapi 5, the shared population strategy is not supported anymore, so components and dynamic zones must be explicitly populated using `on` fragments.

Use API parameters to refine your Strapi REST API queries.

Strapi policies are functions that execute specific logic on each request before it reaches the controller. Policies can be customized according to your needs.

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

Use the REST API to manage the order of relations

Learn more about requests and responses for Strapi, the most popular headless CMS.

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.

Strapi routes handle requests to your content and are auto-generated for your content-types. Routes can be customized according to your needs.

Strapi services are a set of reusable functions, useful to simplify controllers logic.

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

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

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

Upload any kind of file on your server or external providers.

Strapi webhooks are user-defined HTTP callbacks used by an application to notify other applications that an event occurred.

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