Minctrl Docs
SDKs

SDKs

Two official SDKs — TypeScript and Python — thin typed clients over the Minctrl REST API, and which parts of the API they do not cover yet.

Minctrl ships two official SDKs: a TypeScript client whose request-body types are generated from the OpenAPI schema, and a hand-written Python client. Both are thin — each method is one route — and both were written before processes became company-owned, so they lag the API in the places listed below.

Both wrap the same REST API you can call with curl (see the API reference). Nothing the SDKs do is impossible over plain HTTP — they give you types, auth handling, and ergonomics.

Which one to use

TypeScriptPython
Use whenNode.js / Deno / Bun services, Next.js and other web backends, edge/serverless functionsData, ML, and back-office automation; scripts, notebooks, and orchestration jobs
TypesFull TypeScript types from the schemaType hints / typed models from the schema
AuthBearer token from /auth/*Bearer token from /auth/*

Pick the one that matches your runtime. Both cover registering and authenticating, connectors, and reading and resuming process runs. Neither wraps importing or saving a process yet, nor starting a run with draft: true; each SDK page shows the plain HTTP call to use until it does.

Same tokens, same governance

Both SDKs authenticate with the same bearer token the REST endpoints use, and they hit the same governed engine — gates, parking, and shadowed connectors behave identically no matter which SDK (or raw curl) starts the run.

On this page