Stateful test emulator of the Payload collection REST API with seeded data
Tools that talk to the Payload CMS REST API 26
Code that runs apart from your Payload server and reaches it over HTTP: typed clients, n8n and Zapier connectors, an offline emulator and token checks.
Type-safe client for the Payload REST API with CRUD, auth and file uploads
Vue composable that wires a Payload Live Preview into a Vue frontend
Client SDK that streams live Payload draft edits into a frontend preview
Migrates WordPress posts, pages, media, SEO and redirects into Payload
Angular query builder that sends list queries to Payload and other backends as signals
CLI and terminal UI to create and manage multi-tenant Payload sites from one backend
Lets Puck components pull filtered Payload collection items into a resolved prop
Signed client for the VAP API, plus a Payload plugin for storefront sign-in and checkout
Renders Blockwright layouts as React Server Components
Lets AI agents and scripts read, edit and sync Payload content from the command line
Command-line SEO checks and REST sync for Payload content, built for AI agents
Typed custom operations for Payload with a client and server-side contract
Audits a Payload instance for data leaks by probing collections and GraphQL anonymously
Config guardrails and DTO helpers that keep Payload API responses consistent
Type-safe client for querying Payload from client-side React components over HTTP
Command-line client for managing Payload documents, media and auth from a terminal
n8n community node that reads and writes collections, globals and auth through the REST API
Generates TypeScript types, API clients and React routes from Payload collections
Typesafe REST API client for Payload collections, globals and custom endpoints
About these packages
Each of these works from outside Payload, over HTTP.
- Calling the API: Payload SDK, the two REST Clients and Type-Safe API Client, with more among the API clients
- Automating without code: n8n Node reads and writes collections and globals, and Zapier Apps generates a Zapier integration from your collections
- Testing without a CMS: Emulator fakes the collection REST API, seeds predictable content and can inject errors or slow replies
- Trusting a token: External JWT Validation checks Payload-issued tokens locally, so a separate service keeps working when Payload is unreachable
- Checking exposure: Security probes a running site for data anyone can read without logging in
The official Live Preview client and several content CLIs use REST as well. Plugins that change the API on the server, such as OpenAPI generators or field selection, are under REST plugins.



