Create a LitPage Workspace Key
Find Workspace Keys in LitPage, choose Read only or write access, copy the key, and verify or revoke it for Management v2 and CLI use.
LitPage calls the credential for Management v2 and the CLI a Workspace Key. You need one for authorized CMS reads and writes. Public Delivery v1 reads work without a credential. Your Builder login token signs you in to the app, and a preview grant opens a specific unpublished revision.
Create a key in Builder
- Sign in to LitPage Builder and switch to the workspace that owns the target site. Workspace owners and admins can list, create, and revoke keys.
- Select Manage API Keys on the workspace dashboard or open Workspace Keys. Select Create Key.
- Enter a Name for the integration, up to 80 characters. Choose a Type. Live is the form default. Read only allows
content:read. Live and Test both allowcontent:readandcontent:writein the current workspace. Treat Test as write access to those sites. - Set Expires at to a future date and time if the integration needs a deadline. Leaving it blank creates a key with no expiration.
- Create the key and copy the full value before closing the dialog. The full key is shown once. The list shows a masked value afterward.
A key created here applies to the workspace's sites. The form has no single-site selector. Load the key from a secret store into your server, shell, or CI environment as LITPAGE_WORKSPACE_KEY. Keep it out of browser code, Git, screenshots, and logs.
Verify the key
curl --fail-with-body 'https://build.lit.page/api/v2/me' --header "Authorization: ApiKey ${LITPAGE_WORKSPACE_KEY}"
GET https://build.lit.page/api/v2/me requires the Authorization header shown above. It takes no path or query arguments and no body. HTTP 200 returns the v2 envelope with an identity object in data. Check its scope string, workspaceId, type, permissions array, and accessibleSitesCount number. expiresAt is an ISO datetime string or null. defaultSiteSuggestion is a site object or null and can reflect the last-used site. Confirm the target explicitly through site discovery.
Revoke or replace a key
In Workspace Keys, use the active key's Revoke action and confirm. Requests using that key will then fail authentication. If you lose the full value, create a replacement, update the integration, then revoke the old key.
On 401, check that you sent the full key with the ApiKey scheme and check expiration and revocation in Builder. A 403 on key management in Builder can indicate you lack the owner or admin role. A 403 from a content write can indicate read-only permission or site access trouble. Follow the API quickstart to check a key against its sites without writing content.