Casewelt operators
Our staff. They see every organisation, issue channel credentials, and handle the platform. Customers never sign in here.
Selling Casewelt
Some firms want Casewelt inside a practice system they already run. Casewelt issues a channel credential that can create an organisation and nothing else. It is not the customer’s administrator. It is not Casewelt’s operator console. Billing can later follow the partner who opened the tenant.
Three doors, kept apart
Our staff. They see every organisation, issue channel credentials, and handle the platform. Customers never sign in here.
Yours. You exchange it for a short-lived token and may only create or read the tenants you opened. You cannot open a customer’s files with it.
The customer’s. Once the organisation exists, their own automation uses a separate client, scoped to that organisation alone.
What you send
You ask Casewelt to create the organisation, on a host we issue. The first person gets a way to sign in. From then on, the customer runs their own people, files and billing inside that tenant.
If you try to create a plan you are not allowed to sell, Casewelt refuses. If you send the same creation twice, you should get the same organisation — not a duplicate firm.
POST /v1/oauth/platform-token
{ "grant_type": "client_credentials",
"client_id": "cwpp_…",
"client_secret": "cwps_…" }
POST /v1/platform/tenants
Authorization: Bearer …
{ "display_name": "North Chambers",
"plan_code": "business" }
What this is for
Your product remains the place the customer does their craft. Casewelt remains the place the files are governed. The channel credential is the handshake between those two jobs. Secrets are shown once. Rotate them when someone leaves.
Organisation APIs — files, shares, signatures — are documented separately. Channel tokens are refused on those paths.
Work the contract
We will walk create, host, first sign-in, and the error you should see if the plan is not allowed.