Use the Lemhi API and its developer documentation

For a Tenant Admin, or a developer at your MSP, connecting another tool to Lemhi. When you're done, you have an API key and know where the API reference lives.

The full reference, with every endpoint, request and response, is at developers.lemhi.ai. This article covers the parts inside Lemhi: creating, holding and revoking keys.

What the API covers

The Lemhi public API is a REST API at https://api.lemhi.ai, versioned by path (/v1). With it you can list your clients and read their playbooks, AI tools, use cases, latest AI intel report and Compass summary. You can also list, create and update Compass tasks and check off their steps. The reference has the full list.

Create an API key

You need the Tenant Admin role.

1. In Lemhi, go to Settings > API Keys.

2. Select Create API key.

3. Enter a Name. Name it after the integration that will use it, for example CRM integration.

4. Choose a Scope:

   • Read-only allows every read request.

   • Read and write also allows creating and updating, for example new Compass tasks.

5. Select Create key.

6. Copy the secret. Lemhi shows it once: "Copy this secret now. It will not be shown again."

Check: The key is listed with its name, scope, the start of the key, and Last used reading Never until the integration first calls the API.

If API Keys isn't in Settings, your login isn't a Tenant Admin, or the API isn't turned on for your account yet.

Use the key

Send the key on every request in the Authorization header:

Authorization: Bearer <your API key>

Call GET /v1/me first. It returns the key's name, scope and MSP, so you know the key works and which account it belongs to. Rate limits, retries and idempotency are in the reference.

Revoke a key

On Settings > API Keys, select Revoke on the key's row and confirm. Revoking takes effect immediately, and any integration using that key stops working. The key stays in the list marked Revoked, as a record. A revoked key can't be turned back on: create a new one and update the integration.

Use one key per integration, so you can revoke one without breaking the others.