Decap CMS Git Backend API
Decap CMS communicates with Git hosting providers (GitHub, GitLab, Bitbucket, Azure, Gitea) through their REST and GraphQL APIs to read, create, update, and delete content entries, manage media file uploads, and orchestrate editorial workflows. The Decap client library wraps these provider APIs; there is no standalone Decap REST API server — all operations pass through the configured backend. Decap Turbo augments this with a database proxy that caches content and reduces direct Git API round-trips for improved performance and reduced rate-limit exposure.
Documentation
Documentation
https://decapcms.org/docs/intro/
Authentication
https://decapcms.org/docs/authentication-backends/
Other Resources
BackendsOverview
https://decapcms.org/docs/backends-overview/
GitHubBackend
https://decapcms.org/docs/github-backend/
GitLabBackend
https://decapcms.org/docs/gitlab-backend/
GitGatewayBackend
https://decapcms.org/docs/git-gateway-backend/
Collections
https://decapcms.org/docs/collection-types/
Widgets
https://decapcms.org/docs/widgets/
EditorialWorkflow
https://decapcms.org/docs/configuration-options/#publish-mode
MediaLibrary
https://decapcms.org/docs/media-library/
ChangeLog
https://github.com/decaporg/decap-cms/releases