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.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/decap-cms-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑
aid: decap:decap-cms-api
name: Decap CMS Git Backend API
description: '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.

  '
humanURL: https://decapcms.org/docs/intro/
baseURL: https://api.github.com
tags:
- Content Management
- Git Backend
- Editorial Workflow
- Media Management
properties:
- type: Documentation
  url: https://decapcms.org/docs/intro/
- type: BackendsOverview
  url: https://decapcms.org/docs/backends-overview/
- type: GitHubBackend
  url: https://decapcms.org/docs/github-backend/
- type: GitLabBackend
  url: https://decapcms.org/docs/gitlab-backend/
- type: GitGatewayBackend
  url: https://decapcms.org/docs/git-gateway-backend/
- type: Collections
  url: https://decapcms.org/docs/collection-types/
- type: Widgets
  url: https://decapcms.org/docs/widgets/
- type: EditorialWorkflow
  url: https://decapcms.org/docs/configuration-options/#publish-mode
- type: MediaLibrary
  url: https://decapcms.org/docs/media-library/
- type: Authentication
  url: https://decapcms.org/docs/authentication-backends/
- type: ChangeLog
  url: https://github.com/decaporg/decap-cms/releases
- url: graphql/decap-graphql.md
  type: GraphQL