Use the Payload CMS CLI from KosmoKrator to call Payload CMS tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.
Payload CMS can be configured headlessly with `kosmokrator integrations:configure payload-cms`.
# Install KosmoKrator first if it is not available on PATH.curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash# Configure and verify this integration.kosmokrator integrations:configure payload-cms --set api_token="$PAYLOAD_CMS_API_TOKEN" --enable --read allow --write ask --jsonkosmokrator integrations:doctor payload-cms --jsonkosmokrator integrations:status --json
Credentials
Authentication type: API tokenapi_token. Configure credentials once, then use the same stored profile from
scripts, coding CLIs, Lua code mode, and the MCP gateway.
Key
Env var
Type
Required
Label
api_token
PAYLOAD_CMS_API_TOKEN
Secret secret
yes
API Token
base_url
PAYLOAD_CMS_BASE_URL
Text text
no
Base URL
Call Payload CMS Headlessly
Use the generic call form when another coding CLI or script needs a stable universal interface.
Every function below can be called headlessly. The generic form is stable across all integrations;
the provider shortcut is shorter but specific to Payload CMS.
payload-cms.payload_cms_list_collections
Read read
List all collections defined in the Payload CMS instance.
Returns each collection's slug, labels, and field configuration.
List documents in a Payload CMS collection. Supports pagination (limit, page),
sorting, and filtering via the where parameter.
Returns document IDs, timestamps, and field values.
Create a new document in a Payload CMS collection. Provide the collection slug
and a JSON object of field values. The document is created as a draft by default
(if versions are enabled on the collection).
List documents in a Payload CMS collection. Supports pagination (limit, page),
sorting, and filtering via the where parameter.
Returns document IDs, timestamps, and field values.
Create a new document in a Payload CMS collection. Provide the collection slug
and a JSON object of field values. The document is created as a draft by default
(if versions are enabled on the collection).
Headless calls still follow the integration read/write permission policy. Configure read/write defaults
with integrations:configure. Add --force only for trusted automation that should bypass that policy.