Each release also ships as a versioned minikai SDK for Python and TypeScript, so the version numbers below match the
SDK you install. We keep things backwards-compatible wherever we can, so pinning to a version is safe.
Nullable schema representation updated
v1.8.1 Nullable properties that reference another schema now express null via an explicit enum: [null] branch in
their oneOf list, instead of a top-level nullable: true flag, from an OpenAPI generator upgrade. Behaviour is
unchanged and this is a safe upgrade.
Skill assets report their size
v1.8.0 Each skill asset now carries a size field (in bytes), so you can display or budget storage without
downloading the file first.
Explicit type on nullable enum fields
v1.6.1 Nullable enum fields now declare "type": "string" next to their oneOf reference in the spec, from an
OpenAPI generator upgrade. Behaviour is unchanged and this is a safe upgrade.
Restore an archived workspace skill
v1.7.0 Return an archived skill to active with POST /Skills/{id}/restore. The skill becomes available to the
workspace again and regains standard retention. Only archived skills can be restored.
Manage workspace skills
v1.6.0 Create, list, update and delete workspace skills via the new /Skills endpoints. Skills start as drafts,
activate on POST /Skills/drafts/{id}/submit, and carry assets uploaded through POST /Skills/{id}/assets. Listing
returns summaries of active skills (fetch a skill by id for its content and assets); workspace admins also see drafts
and archived skills.
Filter records by a content field
v1.5.4 Pass contentFilters=Key=Value on GET /Records to return only records whose content has that key set to
that value, and repeat the parameter to require several at once. The key matches exactly, the value case-insensitively.
Tidier nullable types in the spec
v1.5.2 Nullable fields now describe themselves more cleanly in the OpenAPI document. Nothing changes on the wire and the SDKs behave exactly as before.
Search Minis by client management ID
v1.5.1 A Mini’s identities can now carry a cms_id, the number your client management system uses, so you can look
a person up by it the same way you would by any other identifier. Available wherever you read or create Minis
(GET/POST /Minis and POST /Minis/external).
Records link both ways
v1.5.0 Relate one record to another and we add the matching link back on the other record for you, and keep the two
in sync as you add, change, or remove them. There are three new ways to describe a link, too: supersedes,
superseded-by, and duplicated-by.
Sort Minis by name
v1.4.0 Browsing Minis, you can now order them alphabetically with name_asc or name_desc, alongside the existing
sorts.
Point one record at another
v1.3.0 Record relations can now name the record they point to: set targetRecordId and choose how the two relate,
either duplicate-of or relates-to. relationship used to be free text; it’s now one of those values, and it’s
required.
Get a total count with your records
v1.2.0 Add includeTotalCount=true to GET /Records and the response tells you how many records match in total,
not just how many came back on the page. Useful for a “showing 20 of 340” line, or to know there’s anything to export
before you start.
Replace attachments across many records at once
v1.1.0 New PUT /Records/batch/attachments swaps out the attachments on a whole set of records in one call, pairing
files to records by position and de-duplicating the same way the single-record call does.
File uploads through the SDKs now work
v1.0.2 Uploading a file through the Python or TypeScript SDK now sends it as a real file. Before this, the bytes were folded into a plain form field and never attached, so uploads came through empty. Upgrade to pick up the fix.
Python and TypeScript SDKs
v1.0.1 The minikai SDKs for Python and TypeScript are now published, so you can call the API from typed client
libraries instead of hand-rolling HTTP.
The Minikai API is live
v1.0.0 The first stable release, served under /api/v1. Read and write the records, Minis, labels, and users in
your workspace.