Developer access
If someone is building software that talks to your teammates, this page is where you create the API key they’ll need. For everyone else, it’s a page you can safely ignore.
Where to find it
Section titled “Where to find it”In the Portal, open Settings, then choose the Developer tile (“API tokens and endpoints”). You’ll land on a page with a back arrow to Settings; the first section, API Tokens, is the one that matters for most people.
The API Tokens section, top to bottom:
- Teammate picker — choose which teammate the keys belong to. Keys are tied to one teammate.
- Generate API Token — creates a new key for the selected teammate.
- The key list — each key shows its name, a masked preview (
hclip_••••…), when it was created, and when it was last used.
Create a key
Section titled “Create a key”Pick the teammate
Use the picker at the top right to choose which teammate this key is for. A key only works for the teammate you pick.
Press Generate API Token
The button creates a fresh key and reveals it once, right in the list.
Copy it straight away
Use the copy icon to copy the full key, then hand it to your developer through a safe channel. After you leave the page it’s masked for good — you can’t see it again.
Turn a key off (Revoke)
Section titled “Turn a key off (Revoke)”Each key in the list has a Revoke button. Pressing it switches that key off permanently — any software still using it stops working right away. Use it when a key is no longer needed, or the moment you suspect it has been shared too widely or leaked. Revoking one key never affects your other keys or your teammates’ day-to-day work.
Where the full developer details live
Section titled “Where the full developer details live”This page is the front desk — it hands out and cancels keys. The instructions a developer follows (how to use a key in code, what endpoints exist, and the Webhook and MCP sections further down this page) live in the separate Developer / API reference, written for people who code. Keeping it apart is deliberate: the Portal Guide stays jargon-free, the reference stays complete.
A quick word on privacy
Section titled “A quick word on privacy”Creating a key doesn’t connect your email, add a payment card, or send anything on its own. Ask before sending is ON; nothing goes out without your OK. A key only lets your own software ask a teammate for work, the same way you do in Chat — and approvals work exactly the same way.
What if it isn’t working?
Section titled “What if it isn’t working?”- No teammates in the picker? You may not have created a teammate yet. Hire one first, then come back.
- Lost the key? It’s shown only once. If you didn’t copy it, Revoke it and Generate API Token again.
- Your developer says the key “doesn’t work”? Check it’s the key for the right teammate, and that it hasn’t been Revoked.
- Unsure what the Webhook or MCP sections are? They’re for developers — you can ignore them. Your developer will know (the Developer reference explains them).
Still stuck? See Getting help.
Do I need an API key to use AImetier?
No. You only need a key if someone is building software that connects to your teammates. To chat, upload documents, or connect everyday tools, you never touch this page.
Why is the key shown only once?
It’s a safety measure — like a password, it’s revealed at creation and then stored hidden. Copy it right away and keep it somewhere safe. If you lose it, revoke it and make a new one.
Can one key work for all my teammates?
No. Each key belongs to a single teammate. Use the picker to choose the teammate, then create a key for that one. Make a separate key per teammate if you need several.
Is creating a key the same as connecting a tool?
No. To connect tools and data sources (like email or a calendar), use the Connectors page. A developer key is only for custom software your own developer is building.
What if a key leaks?
Press Revoke next to it straight away — that disables it for good — then Generate API Token to create a replacement and share the new one safely.