Authentication

The Workspace API authenticates with API keys. A key is tied to a workspace and acts with admin privileges, so treat it like a password.

Creating an API key

1. Sign in as a workspace admin.
2. Open your workspace API key settings.
3. Create a new key and give it a descriptive name (e.g. “Zapier”, “ETL job”).
4. Copy the key now — the full value (ml_live_…) is shown once. After that, only a masked hint is displayed.

Store keys securely

The full key is shown only at creation. Save it in a secrets manager or environment variable. If you lose it, delete the key and create a new one.

Using a key

Send the key as a Bearer token on every request:

export MIXERLEAD_API_KEY="ml_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

curl https://ai.mixerlead.com/api/ai/models \
  -H "Authorization: Bearer $MIXERLEAD_API_KEY"

Node.js (fetch)

const res = await fetch("https://ai.mixerlead.com/api/ai/models", {
  headers: { Authorization: `Bearer ${process.env.MIXERLEAD_API_KEY}` },
});
const data = await res.json();

Python (requests)

import os, requests

res = requests.get(
    "https://ai.mixerlead.com/api/ai/models",
    headers={"Authorization": f"Bearer {os.environ['MIXERLEAD_API_KEY']}"},
)
res.raise_for_status()
print(res.json())

Scoping to a project

By default, requests use your workspace’s default project. To target a specific project, add the X-Project-Id header:

curl https://ai.mixerlead.com/api/agents \
  -H "Authorization: Bearer $MIXERLEAD_API_KEY" \
  -H "X-Project-Id: <your_project_id>"

Managing & rotating keys

• List your keys to see their names, masked hints, and last‑used time.
• Rotate by creating a new key, updating your integration, then deleting the old one.
• Revoke a key by deleting it — it stops working immediately.

One key per integration

Issue a separate key for each integration or environment. That way you can rotate or revoke one without disrupting the others, and last‑used timestamps tell you what’s active.

Errors

Situation	Response
Missing or malformed key	401 Unauthorized
Unknown / revoked key	401 Unauthorized
Rate limit exceeded	429 Too Many Requests

See Errors & rate limits for the full reference.

Related

API overview Base URL and conventions.

Members & roles Who can manage keys.

Security & trust How MixerLead protects credentials.