API Keys
Feature video
Who is this for?
- Technical teams connecting Leexi to their own tools, scripts, or internal products.
- Administrators automating the retrieval of calls, meeting notes, and meeting events.
Permissions and licenses
- The public API is available from the AI Meeting plan onwards.
- Viewing keys requires the permission to read API keys; creating and editing them requires the write permission.
How to use it
Open the API Keys page
Go to Settings > Advanced settings > API Keys. For each key, the list shows its name, access rules, description, permissions, creation date, last use, and the person who created it.
Create a key
Click "Add". Leexi generates a key ID and a secret. Copy them right away by clicking each field: the secret is only visible at creation.
Name and describe the key
Fill in a name and a description that identify the tool or use case involved. This is what lets you find and revoke the right key later.
Choose the permissions
Select the permissions granted: read and write calls, read and write meeting events, read users, teams, and company. Only enable what the tool actually needs.
Set the access rules
Three modes are available:
- Linked to a user: the key inherits the access of the chosen user.
- Access to everything: the key can access every call in the company.
- Custom access: after saving, you are redirected to the Access rules page to define the exact scope.
Authenticate your requests
Use the ID and the secret as HTTP Basic authentication on https://public-api.leexi.ai/v1/. Endpoints, parameters, and response formats are described in the public API reference.
Going further
- The "Last used" column helps spot dormant keys, which are worth deleting when the matching tool is no longer in service.
- The public API is limited to 50 requests per minute, and to 10 requests per minute for call creation.
- A key's name, description, permissions, and access rules can be changed at any time by clicking its row: the ID and the secret, however, never change.
- Webhooks cover the opposite need: instead of querying the API, you receive an event as soon as a call has been processed.
Frequently asked questions
Things to watch out for
- A key grants access to data without user authentication: keep the secret in a secret manager, never in a code repository or a message.
- The "Access to everything" mode ignores team boundaries: reserve it for integrations that genuinely need it.
- A key stays valid even if the person who created it leaves the company: review your keys whenever someone leaves.
- Write permissions allow creating and modifying data in Leexi: grant them sparingly.