Legacy API Key
Your original API key is displayed at the top of this section. This key continues to work as before and is not affected by the introduction of API tokens.
Individual API Tokens
The API Tokens section allows you to create and manage multiple named tokens for different integrations. This is useful when you connect several systems to LILT (e.g., a CMS connector, a CI pipeline, and an internal tool) and want to manage each one independently. Creating a token- Click Create Token.
- Enter a descriptive name (e.g., “Contentful connector”).
- Select who this token is for. Typically this will be the token creator but could be another customer contact or admin
The API key permissions will match the permissions of the user role being assigned that key - Optionally set an expiration date.
- Click Create. The full token is displayed once — copy it immediately and store it securely. It cannot be retrieved later.
lilt_abc1...), creation date, expiry, and when it was last used.
From this list you can:
- Revoke a token to permanently disable it without affecting other tokens.
- Rotate a token to generate a new secret while keeping the same name and configuration. The new token is shown once for copying.
- Each connector has it’s own API key
- Each user gets their own API key (e.g. if I’m using an API key for some sort of integration, I generate a new API key)
- You can only access/copy an API key at the time of creation. You can’t go back and copya key after it’s been initially generated.
- Temporary uses should have temporary keys but connectors should have non-expiring keys or expiration dates long in the future (because of the risks of connector API keys expiring)
?key= query parameter or Basic Auth) as the legacy key, so no changes are needed in existing SDKs or CMS plugins. For more information, see our API documentation.