The Admin Panel API exposes register, bootstrap, and registerTrads hooks to inject React components and translations into Strapi’s UI. Menu, settings, injection zone, reducer, and hook APIs let plugins add navigation, configuration panels, or custom actions.
The Content Manager APIs reference lists the APIs available to plugins for adding actions and options to the Content Manager List view and Edit view.
By using Swagger UI, the API documentation plugin takes out most of your pain to generate your documentation.
Configure Strapi Cloud to use a third-party email provider.
Find some answers and solutions to most common issues that you may experience when working with Strapi.
Use a GraphQL endpoint in your Strapi project to fetch and mutate your content.
Learn how to create and configure components for your Strapi plugins
Learn how to pass data from server to admin panel with a Strapi plugin
Learn how to store and access data from a Strapi plugin
The in-app Marketplace lists plugins and providers with badges, search, and “More” links to detailed Strapi Market pages. This documentation outlines browsing cards and following provider-specific instructions to install new integrations.
Learn how to use the Plugin SDK to build and publish a Strapi plugin
Reference documentation for Strapi's Plugin SDK commands
Learn more about the structure of a Strapi plugin
Strapi plugins have a single entry point file to define their configurations.
Existing plugins can be overriden by placing code in /src/extensions or using global register/bootstrap hooks. Instructions in this documentation cover reshaping plugin content-type schemas or server logic — altough upstream updates may break extensions.
The present page is intended to be used as a short summary of everything to consider if you are a plugin developer upgrading your plugin from Strapi v4 to Strapi 5. The page quickly describes the changes affecting plugins and links to additional resources where necessary.
Configure Strapi Cloud to use a third-party upload provider.