An API key lets your own software — an HR system, a reporting script or an AI agent — work with your organization's data without a person logging in. The key belongs to the organization, not to you, so it keeps working when you change jobs, and you can revoke it in one click.
Who can do this
Available to organization Admins. Open Organization settings → Integrations. Developers create their keys in Applications → Integrations.
See your keys
The API keys card lists every key of the organization with its Scope, Roles, expiry date, when it was Last used and its Status (Active, Revoked or Expired). Under the name you see only the beginning of the key, never the whole value.
Create a key
- 1Open Organization settings → Integrations.
- 2Click Create key.
- 3Under Name, name it after the tool that will use it — that is the name you will see in the request log.
- 4Under Roles, pick what the key gets: Admin, Analyst or Device admin. A key can never do more than you can, so you only see the roles you hold yourself.
- 5Under Scope, pick Read only or Read and write.
- 6Under Valid for, pick 30, 90 or 365 days.
- 7Click Create key.
We show the key once, right after creating it. Copy it into your password manager or your secret store before closing the window. If you lose it, rotate the key and use the new one.
Treat the key like a password
Anyone holding it can read your organization's data within the roles you granted. Never paste it into a chat, a ticket or a public repository.
What the key looks like
Every key starts with sk_live_, for example sk_live_7Hq2mZk1_…. The panel stores only its hash and the visible prefix, which is why we cannot show you the full key again.
Send it in the Authorization header:
Authorization: Bearer sk_live_7Hq2mZk1_…
Roles and scope
- Roles decide what data the key sees — exactly the same rules as for a person in that role.
- Scope decides what it may do: a read-only key is rejected with
403on every write. - The key works only inside the organization it was created in. It cannot reach the panel (
api/web) at all.
Expiry and rotation
A key stops working the moment it expires. Both actions below are in the menu at the end of an active key's row.
- Rotate gives you a new key value while the old one keeps working for another 24 hours — enough to redeploy your tool without downtime.
- Revoke kills a key immediately; every call with it is rejected within a minute. This cannot be undone.
Limits
- 10 active keys per organization and per context.
- 120 requests per minute per key. Above that the API answers
429with aRetry-Afterheader.
The request log
The Request log card on the same page lists every call made with a key of this organization: the key, the method and path, the response status, how long it took and whether it came over REST or MCP. Filter it by Key or by Status when you are debugging an integration — a 429 means the key hit the rate limit. Entries are kept for 90 days.
The API reference
The full list of endpoints, request and response shapes is in the API reference: api.skillsive.com/core/docs/v1. The API documentation button on the Integrations page opens the same page.
Connect an AI agent (MCP)
The same key authenticates you to the Skillsive MCP server at https://api.skillsive.com/core/mcp, which exposes the API as tools an agent can call directly.
Claude Code — one command in your terminal:
claude mcp add --transport http skillsive https://api.skillsive.com/core/mcp --header "Authorization: Bearer sk_live_…"
Cursor — add the server to ~/.cursor/mcp.json (or .cursor/mcp.json in the project):
{
"mcpServers": {
"skillsive": {
"type": "http",
"url": "https://api.skillsive.com/core/mcp",
"headers": { "Authorization": "Bearer sk_live_…" }
}
}
}
Claude.ai and ChatGPT connectors
The connectors in the Claude and ChatGPT web apps require OAuth sign-in, which Skillsive does not support yet. Agents that authenticate with a header — Claude Code, Cursor, and your own agents — work today.
FAQ
I closed the window before copying the key. Can I see it again?
No — we store only its hash. Open the key's menu, click Rotate and copy the new value.
Which role should an HR or reporting tool get?
Admin. Reading trainees, course completions and certificates requires an Admin key — an Analyst key can only read the organization's own details. To keep the key harmless, give it the Read only scope: it can read but never change data.
Does a key stop working when the person who created it leaves?
No. The key belongs to the organization. Revoke it yourself when the tool is no longer used.