An API token lets your own scripts and integrations talk to the liveplanner API as you, outside the editor. Tokens belong to your liveworkspace account, so one token works with the API and MCP server of every liveworkspace app, liveplanner included. A token carries your account's full read and write access unless you make it read-only, so treat it like a password.
To connect an AI tool like Claude rather than write your own script, see Connect an AI Tool (MCP): it creates and uses one of these tokens for you. So does the liveplanner CLI when you sign in with liveplanner auth login.
You need an account
API tokens are a signed-in-only feature. The editor, sharing, and real-time collaboration all stay account-free for guests, but tokens require signing in, the same as teams.
Creating a token
Tokens are made on liveworkspace.app. In liveplanner, open Settings (the gear near the end of the bottom bar), choose Account, then API Tokens, and choose Manage API Tokens to get there.
Name the token, switch on Read-only if it only needs to look, and create it. Its secret is shown once, right after you create it: copy it then, because it is never displayed again. If you lose the secret, revoke the token and create a new one.
What a token can do, and for how long
- Access: a token has your account's read + write access to plans and folders, including your teams' shared libraries, or read access only if it is read-only. It can't manage teams or your account: those are done on liveworkspace.app, signed in.
- Lifetime: every token lasts six months, then expires. Rotate by creating a fresh token before the old one lapses.
- Limit: you can have up to 20 tokens at once, across every liveworkspace app. Revoke one to free a slot.
Using a token
Send the token as a bearer header to the API, which lives under /api on your liveplanner host (https://liveplanner.app/api on the hosted service):
# List your projects
curl https://liveplanner.app/api/projects \
-H "Authorization: Bearer lwt_your_token_here"
Every request authenticated this way acts as your account, with the same read and write access you have in the editor. A few rules are particular to tokens: edits go through changesets rather than whole-tab saves, a token can't delete a plan's last tab, and each token has its own rate limits. Keep the Authorization header on each request; there is no separate login step.
For what you can call and how, see the Developers section: Authentication, worked examples, and errors and rate limits. The full machine-readable reference is published at /api/openapi.json.
Viewing and revoking tokens
Your tokens are listed on liveworkspace.app, with when each was created, last used and expires. Revoke one there. liveplanner stops accepting it within a minute, and ends any workbench pairing made with it within a few minutes. Deleting your account also removes all of your tokens, along with the rest of your data.
Keep tokens out of source control and shared logs. If one might have leaked, revoke it and create a replacement, no need to change anything else about your account.
Was this article helpful?