API

The Papermark API is a small, deliberately boring REST surface: HTTP

JSON + bearer tokens. 43 operations across 6 resources. No SDK, no build step, no client library to keep in sync.

curl https://api.papermark.com/v1/documents \
  -H "Authorization: Bearer pm_live_…"

What's here

Page	Read first if…
Getting started	You want to make your first call right now
Authentication	You're integrating from a third-party tool (OAuth) or building CI
Scopes	You're picking what a token can do
Rate limits	You're building anything that polls or batches
Errors	You hit one and want to know what `code` means
Reference	You want every endpoint, request shape, response shape, generated from `openapi.json`

Datarooms: create, list, get, update, delete; attach documents; manage dataroom folders. The primary unit for sharing a set of documents under one access boundary.
Documents: upload, list, get, search, update, delete; manage versions. Standalone or attached to one or more datarooms.
Folders: organize standalone documents into folders outside any dataroom. List, create, get, update, move, delete (with optional cascade).
Links: create, list, get, update, revoke share links pointing at either a document or a dataroom, with passwords, expiry, email gating, download permission.
Visitors: list visitors and their view history.
Analytics: aggregate stats per document, link, dataroom, and per individual view.

The full spec is at /docs/openapi.json, which is also what generates the reference pages on this site, so nothing can drift.

CLI: papermark on npm. Same surface from a terminal, with --json output for pipelines.
MCP server: drop the same surface into Claude or ChatGPT so an agent can act on your behalf.