Developers
The product you see is the product you call.
Casewelt’s organisation API is the same work as the portal and the admin console: files, shares, signatures, people, audit, events. Automation is a named principal with scopes. Recipients still use the public doors. Nobody is handed a storage address.
Start here
Read the map, then the walks.
API reference
Areas, scopes, and what is deliberately out of this contract.
Open the map →Authentication
API users, client credentials, secrets shown once, humans refused.
Mint a token →Files & transfer
Upload sessions, named versions, new documents, inbound requests.
Move bytes →Example
Create a folder once, even when the network makes you ask twice.
The folder lives under a workspace. An idempotency key is the request’s name across retries. You do not get a second Board pack and a doubled audit line.
Read the file APIPOST /v1/workspaces/{ws}/folders
Authorization: Bearer …
Idempotency-Key: 7a1f…
Content-Type: application/json
{
"name": "Board pack",
"parent_folder_id": null
}Identity, machines and events
Plug Casewelt into the systems you already run.
People sign in through your identity provider on Business and above. Automation uses API users. Devices can enrol with their own certificates so a scanner never borrows a password. Outbound events are signed, replay-protected and retried for seventy-two hours; administrators can list deliveries and replay a missed one.
The API is versioned REST and JSON. Problem documents distinguish validation, policy denial and state conflict. Organisation administrators can download a Partner API reference from the console: the same contract, printed for that tenant. Recipient traffic stays on the share and signing doors.
Review the contract
Bring the system that should create, listen or sign.
We will mint a scoped client, succeed once, fail on purpose, and read the problem document together.