API Keys
Create an API key when you want an outside tool — Claude Code, a Zapier automation, your own script — to read or act on your Adlyse data on your behalf. An API key is a secret token that lets that tool work with your account the way a password would, so treat it like one.
In one line
Create a key under Admin → API Keys, copy it once, and paste it into the tool you’re connecting.
Keep your key safe
A key carries full access to your workspace’s data — anyone holding it can do what you can. You see a new key’s value only once, so copy it right away and store it somewhere secure. Never drop it into a shared doc, screenshot, or public code repository, and rotate it the moment you see activity you don’t recognize.
Create a key#
Open the API Keys page#
Go to Admin → API Keys in the Adlyse dashboard.
Create the key#
Choose Create API Key and give it a descriptive name — something like “Claude Code”, “Zapier connector”, or “CI pipeline” — so you’ll know later what it’s for.
Copy it now#
The key is shown only this once. Its value starts with mii_prod_ so you can recognize it; copy it and store it somewhere secure before you leave the page.
Paste it into your tool#
The tool you’re connecting will ask for the key. Some send it behind the scenes as a “Bearer” token; you just paste the value.
Turn a key off#
Revoke a key from the same page. It takes effect immediately — any tool still using it is refused on its very next request. Revoke a key as soon as you suspect it’s been exposed.
Rotate a key#
For a connection you’ll keep running a long time, swap keys periodically:
- Create a new key.
- Point the tool at the new key.
- Confirm traffic is flowing to it — the usage stats on the API Keys page show this.
- Revoke the old key.
You can keep several keys active at once, so rotating never causes downtime.
One key per tool#
Every key has full access to your whole organization. Because of that, give each integration its own key — then you can revoke any one of them without breaking the others.
Connect with OAuth instead#
Some AI clients — notably Claude.ai — can connect to Adlyse with a Connect button instead of a pasted key. You approve access once, and the client handles the token for you; it’s tied to your own login and organization. Either way, everything works the same once you’re connected.
See how a key is being used#
Every request a key makes is logged. For each key, the API Keys page shows:
- When it was last used
- How many requests it’s made this period
- Which endpoints it hits most
What to do: glance at this now and then. Activity you don’t recognize is your cue to rotate the key.
Common flows#
- Connect a new tool. Create a key and paste it in.
- Suspect a key leaked. Revoke it and issue a fresh one.
- Keep integrations isolated. Use one key per tool so revoking one never affects another.