API clients and SDKs for Payload CMS 21

Call Payload CMS from another app with the official Payload SDK or a typed REST client. Connect n8n and Zapier, or verify Payload tokens elsewhere.

Type-safe client for the Payload REST API with CRUD, auth and file uploads

Framework-agnostic SDK for inline visual editing on Payload-powered sites

Angular query builder that sends list queries to Payload and other backends as signals

Registers custom drag-and-drop blocks for the Olgax page builder

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

Typed custom operations for Payload with a client and server-side contract

Frontend SDK that lets a site accept inline visual editing from Payload Live Preview

Typed repository classes for collections and globals over the Payload Local API

React chat interface for AI agents backed by Payload

Chat interface components for talking to AI agents

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

Verifies Payload-issued JWTs in external services without calling the CMS

n8n community node that reads and writes collections, globals and auth through the REST API

Strongly typed find, create, update and delete calls with checked where and sort clauses

Generates TypeScript types, API clients and React routes from Payload collections

Typesafe REST API client for Payload collections, globals and custom endpoints

Typesafe REST API client for collections, globals and custom endpoints

Typed REST client for Payload with the same query syntax as the Local API

About these packages

API clients call Payload from code that runs outside it, such as a separate backend or an automation platform. Most of them wrap the REST API with types, so requests and responses match your collections. A few organize Local API calls inside the app instead. Live preview and rich text rendering are among the frontend tools.

What these tools cover

  • The official Payload SDK, a typed REST client for any JavaScript app
  • Type-Safe API Client with Local API query syntax, and REST Client
  • Visual Editor Core and Inline Visual Editor Core for click-to-edit pages
  • External JWT Validation for services that trust Payload tokens
  • Repository classes that group Local API calls per collection
  • An n8n node and a Zapier app generator for automation

Choosing a client

Start with the official Payload SDK when another project needs a typed client. Pick Type-Safe API Client if you want the Local API query syntax over HTTP. REST Client also types calls to your custom endpoints. A service that only needs to know who is calling can verify Payload tokens with External JWT Validation. It does not have to call the CMS for that. Check the supported Payload version on each card before you install.

Frequently asked questions

Do I need an API client if my frontend runs in the same Next.js app?

Usually not. Inside the same app you can call the Local API directly. API clients are for code that reaches Payload over HTTP from another app or service.

Is there an official JavaScript SDK?

Yes. The Payload SDK from the Payload team is a typed REST client for querying a Payload backend from any JavaScript app.

Can I connect Payload to n8n or Zapier?

Yes. A community n8n node reads and writes collections and globals. For Zapier, Zapier Apps generates an integration app from your collections.