Laver documentation#
Laver is a project-management workspace: Kanban boards with configurable columns and sprints, tickets with assignees, priorities and due dates, and a nested wiki with a rich-text editor and full-text search. Everything is scoped to a workspace, and everything the app does is also available over the HTTP API.
These docs cover both audiences. If you are using Laver in a browser, start with
the guides. If you are writing something that talks to Laver — a script, an
integration, an agent — start with the API reference and keep
https://api.laver.app/openapi.json open beside it.
Reading these docs as a machine#
Every page is served twice. The HTML page lives at
/docs/<section>/<page> and the Markdown source it was rendered from lives at
the same path with .md appended:
https://laver.app/docs/agents-and-api/api-reference HTML
https://laver.app/docs/agents-and-api/api-reference.md Markdown source
The Markdown URL is stable, has no navigation chrome around it, and is served as
text/markdown. Fetch that one. /llms.txt lists the whole set.
Conventions used throughout#
Examples use https://api.laver.app as the API base URL and a placeholder
credential:
curl https://api.laver.app/workspaces \
-H "Authorization: Bearer laver_..."
Identifiers in examples are obviously fake — 11111111-2222-4333-8444-555555555555
or a <workspace-uuid> placeholder. Substitute your own.
Where a page needs a particular role or plan, it says so before the first instruction rather than after it.
All sections
Start here
- What Laver is What Laver is for, the handful of objects you work with, and the things it deliberately does not do.
- Quickstart Get from a new account to a working board, a moving ticket, a wiki page, and an invited colleague in about five minutes.
- Your first workspace How to create a workspace, and exactly what it comes with — the starter board, its three columns, the wiki, and who owns it.
Concepts
- Workspaces and boards How workspaces contain boards and boards contain tickets, how board access sits alongside workspace roles, and what the wiki belongs to.
- Statuses and workflow What status columns are, how they are configured per board, what marking one as complete means, and how a ticket moves between them.
Boards and tickets
- Boards Create a board, rename and reorder it, set up its status columns, and archive it — and restore it again — when it is finished with.
- Tickets Create tickets, fill in their fields, move and reorder them, assign people, duplicate them and delete them.
- Comments and files Comment on a ticket, mention teammates, and attach files — including the size limits, allowed types and storage cap.
- Filters and card display Narrow a board down to the tickets you want, and choose what each card shows.
- Sprints Turn a board into a repeating cycle, roll unfinished work into the next sprint, and read back over finished ones.
- Importing from Trello, Jira, ClickUp, Microsoft Planner and a spreadsheet Turn an export from another tool — or your own spreadsheet — into a Laver board, what comes across, and what re-importing does.
- Search the workspace Find a board, a ticket, a comment or a wiki page from anywhere with ⌘K.
- The browser extension File a ticket from the page you are looking at, with a screenshot, a recording of the tab and the URL already attached — installing it, the shortcuts, and what it sends.
Wiki
- Wiki pages Write and organise the workspace wiki — creating pages, nesting them, the editor, images, and how autosave and drafts behave.
- Quick notes Write a thought down without leaving the page you are on — where notes live, who can read them, and how to get one back.
- Document signatures Ask somebody outside the workspace to sign a section of a wiki page — the private link, the blanks they fill in, declining, expiry, and the signed copy both sides keep.
- Diagrams Draw boxes and arrows inside a page, a ticket, a comment or a note — the tools, the limits, and what a diagram is and is not.
Workspaces and access
- Roles and permissions The seven workspace roles and exactly what each one can and cannot do.
- Invitations Inviting people to a workspace, setting their role and board access, and managing invitations until they are accepted.
- Board access How board membership works alongside workspace roles, and what someone can see when they are not on a board.
- API keys Creating, scoping, revoking and safely handling the keys that let scripts and agents act in a workspace.
- Shared secrets Hand a colleague a credential without pasting it into a chat — who can read a secret, what a reveal records, and what happens when somebody leaves.
Administration
- Members and offboarding Changing roles, deactivating or removing people, and what happens to their tickets, keys and seat.
- Billing A free plan and one paid plan, per seat, monthly or annual — what each billing state allows, and what happens when a payment fails.
- Security and your account Passwords, email verification, two-factor authentication, password reset, and signing out everywhere.
- Exports and deletion Getting your data out, and exactly what deleting a workspace or an account does.
- Trash and restore Deleted tickets, comments, wiki pages and attachments are recoverable for 30 days, then destroyed for good.
- Notifications What Laver tells you about, in the app, by email and by push, and how to turn each of it off.
Agents and API
- Agent quickstart From no credentials to safely completing one ticket, in nine copy-pasteable steps.
- MCP server Connect Claude, Cursor or any MCP client to your boards and wiki with one config block and an API key.
- MCP setup by client Where the Laver config block lives in Claude Code, Claude Desktop and Cursor, how each client reloads it, and how to check the connection works.
- Driving a board over the API Reading a board, searching it, and creating, moving, commenting on and labelling tickets.
- Concurrency and polling Why tickets carry a version, what a 409 gives you, and how to follow a board without re-reading it.
- API reference The OpenAPI document, how to generate a client from it, and the authentication, rate limit and paging rules it does not tell you.
- Outbound webhooks Get a signed POST when a ticket changes, instead of polling for it. Events, the signature scheme, retries, and the delivery log.
- Automation rules Store a trigger, conditions and actions against a board over the API. The vocabulary, the limits, and why a rule is a standing grant of its actor's permissions.