Developer API
Read your workspace from your own systems. The API serves the registers kitset already keeps — assets, vendors, systems, people, purchase requests, learning assignments, handovers, transitions, tasks, locations and workplace records — so the data you maintain here can appear in your CMDB, your data warehouse or your service desk without anybody exporting a spreadsheet.
What it is, and what it is not
It is read-only. Nothing you do through this API changes a record. Writing stays in the Management Console, where approvals, evidence and audit trails work the way the product promises.
It is server-to-server. A key reads an entire workspace within the scopes you give it, so it belongs on a server you control. There is no CORS policy and that is deliberate: a key that works from a browser is a key that ends up in one.
It is versioned in the path. Everything lives under /api/v1. When a change would break a client, the new shape goes to a new version rather than into this one.
Getting your first response
Create a key in the Management Console under API keys, choose the scopes the integration needs, and copy the key — it is shown once.
curl https://your-workspace.kitset.io/api/v1/assets \
-H "Authorization: Bearer kitset_sk_live_YOUR_KEY_ID_HERE"
{
"data": [
{
"id": "a3f1...",
"name": "MacBook Pro 14",
"asset_tag": "LAP-014",
"status": "AVAILABLE",
"updated_at": "2026-09-20T09:14:02+00:00"
}
],
"has_more": false,
"next_cursor": null
}
Every list answers with the same three fields: data, has_more and next_cursor. Every single record answers with data alone.
The shape of everything
- Timestamps are ISO 8601 and always carry an offset.
- Money is an integer of minor units, in a field ending
_cents, beside itscurrency. - A reference to a person is an id, never an embedded record. Read
/api/v1/peoplewithpeople:readif you need their name. - Identifiers are opaque strings. Do not parse them.
Where to go next
- Authentication — keys, scopes and what a refusal means
- Pagination and sync — walking a register and keeping it current
- Errors — the one shape everything fails in
- Rate limits — what you may spend
- Endpoint reference — every route and the scope it needs
The machine-readable contract is at /developers/openapi.json.