Settings

API Keys

Create and manage the keys that let your external tools read and write Leexi data through the public API.

Definition: An API key identifies an external tool to Leexi's public API. It defines which data that tool can access and which actions it can perform, without having to share a user's credentials.

Feature video

No video is available at this time.

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

Requires: AI Meeting
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 > 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 and access rules

Check the permissions the tool actually needs, then choose the access rules mode. In Custom access mode, saving redirects you to the Access rules page to define the key's scope. What each permission allows and what each mode lets the key see: see References › Developer › API key scopes.

Authenticate your requests

Use the key's ID and secret in your requests. Endpoint, authentication header and limits: see References › Developer › Public API.

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 per key; the detailed limits are in the public API reference.
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.

Previous and next pages

E-mail templates

Adapt the reminder emails Leexi sends before recorded meetings.

Webhooks

Automatically receive an event in your own systems as soon as a Leexi call has been transcribed and analyzed.