Developer API
Automate Papyro from your own systems
A versioned REST API with an OpenAPI 3.1 spec, scoped API keys and idempotency — plus an MCP server so AI assistants can work inside your workspace.
Versioned REST API
A stable /api/v1 surface for boards, lists, cards (with comments), notes, spaces, helpdesk customers and tickets, and your end users' own reports — documented by a hand-written OpenAPI 3.1 spec your instance serves itself.
MCP server for AI assistants
Any MCP client can read and write your boards and notes through 12 tools — list, create and update cards (move, assign, label), create lists, read and write notes, and triage error fingerprints. Authenticate with OAuth 2.1 (your install is its own authorization server) or a scoped papyro_ key. Every call is audited, and a single admin switch cuts all clients off.
Scoped API keys
Issue papyro_ keys from Settings, send them as a Bearer token or x-api-key header, and grant only the scopes each integration needs.
Error ingestion into boards
Point your services at /api/v1/boards/{id}/fingerprints and Papyro groups the events, tracks first and last seen, fires your webhook and can write a root-cause analysis onto the card. Your own error monitoring, on your own server.
Idempotency & pagination
Cursor pagination and idempotency keys make bulk and retried requests safe and predictable.
Rate limits you can see
Every response carries rate-limit headers, so your client always knows where it stands.
The full interactive API reference ships inside every Papyro instance at /api/v1/docs, with the raw spec at /api/v1/openapi.json. The MCP endpoint lives at /api/mcp and advertises itself through the standard OAuth discovery documents.