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 delete it 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.
Wiki
- Wiki pages Write and organise the workspace wiki — creating pages, nesting them, the editor, images, and how autosave and drafts behave.
Workspaces and access
- Roles and permissions The four 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.
Administration
- Members and offboarding Changing roles, deactivating or removing people, and what happens to their tickets, keys and seat.
- Billing One plan, per seat, monthly or annual — the trial, 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.
Agents and API
- Agent quickstart From no credentials to safely completing one ticket, in nine copy-pasteable steps.
- 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.