API tokens let you connect BookLive to external AI assistants and automation tools on your behalf. Tokens are scoped to MCP (Model Context Protocol) use, which means they authenticate AI clients — such as Claude Desktop or other MCP-compatible tools — so those tools can read your BookLive data, create performances, manage clients, and more. Treat them like passwords: anyone who holds a token can act as you when calling BookLive’s MCP server.
Before You Begin #
- You must be logged in to your BookLive account as a group leader.
- Only you can see and manage your own tokens — tokens are per user, not per group.
Step 1: Open Account Settings #
Click your avatar in the top-right corner of any BookLive page, then select Account Settings from the dropdown menu.
Step 2: Navigate to the API Tokens Tab #
Inside Account Settings, click the API Tokens tab. You’ll see a table listing any existing tokens along with a form to create new ones.
Step 3: Generate a New Token #
- In the Token name field, enter a descriptive name so you can identify this token later — for example, Claude Desktop or Automation Script.
- In the Expires dropdown, choose an expiration window:
- 90 days (recommended) — a good balance of security and convenience
- 30 days or 60 days — shorter-lived for higher-security environments
- 1 year — longer validity for stable integrations
- No expiration — never expires; rotate manually when needed
- Click Generate token.
Step 4: Copy and Store Your Token #
A dialog appears showing your new token. This is the only time BookLive will display the full token value. Copy it immediately using the Copy to clipboard button, then paste it into your MCP client configuration or a secure password manager. Once you dismiss the dialog, the token cannot be retrieved — if you lose it, you’ll need to revoke it and generate a new one.
Viewing Existing Tokens #
The token table shows each token’s Name, Created date, Last used date, and Expires date. If a token has never been used, the Last used column shows Never. An expired token appears in red and will no longer authenticate requests.
Revoking a Token #
To invalidate a token immediately, click Revoke next to it in the table, then confirm in the dialog that appears. Revoking a token cannot be undone — any client using that token will stop working right away. Generate a new token and update your client configuration if you want to restore access.
Tips & Notes #
- One token per use case: Create a separate token for each tool or integration so you can revoke a single one without affecting others.
- Token names are unique per account: You can’t create two tokens with the same name.
- MCP server URL: When configuring an MCP client, the BookLive MCP server endpoint is
https://booklive.com/mcp. Use your token as the bearer token in theAuthorizationheader. - Expired tokens: Expired tokens remain visible in the table so you can see they’ve lapsed. Revoke them to keep your token list tidy.
- Security: If you suspect a token has been compromised, revoke it immediately and generate a replacement.
