The full API surface, three ways. Import the OpenAPI spec into Postman, hit the live Swagger UI, or grab the raw JSON for any other tool. Every endpoint is callable against a sandbox tenant.
All three point at the same OpenAPI 3 document. The sandbox is read-mostly — destructive endpoints are scoped to a per-session tenant so you can't break anything for anyone else.
One click to launch the desktop app and hand it the OpenAPI URL. Postman builds a fully-organized collection with all 524 endpoints grouped by tag.
https://cleen-prod-api.azurewebsites.net/swagger/v1/swagger.jsonbaseUrl environment variable, add an auth token, and start calling.Don't want to install anything? Hit the live Swagger UI in your browser. Every endpoint is documented with example payloads, and the "Try it out" button calls the sandbox directly.
Open Swagger UIHosted on the sandbox itself — same auth and tenant rules as Postman.
The raw OpenAPI 3 JSON — feed it into Insomnia, Bruno, Hoppscotch, OpenAPI Generator, or any tool that speaks the spec.
View swagger.json~1 MB. Right-click → Save As to download.
Set these up once in a Postman environment and every call works without further setup.
https://cleen-prod-api.azurewebsites.netThe sandbox base URL — already wired as a Postman variable if you imported the spec.
eyJhbGciOi... (Bearer)Most endpoints are gated behind a Bearer token. Getting one takes ~60 seconds — you'll create a free demo account, authenticate through Swagger or Postman's lock icon, then copy the token into your environment.
eyJ… — that's your Bearer token. Highlight and copy it.accessToken variable in your Postman environment (Environments → your env → Initial Value column). Save.Authorization: Bearer {{accessToken}} on every request.Tokens expire after ~24 hours. When they do, re-run step 3 and replace the variable value. No real data leaves the sandbox — it's a fresh tenant for each demo signup.
The collection mirrors the same tag structure you see on the codebase page. Hit a tag folder, scan the operations, fire one off.
It's the sandbox build — same code, same endpoints, same response shapes as the production CleenUI license. Data is reset periodically.
Not for anyone else. Every session gets its own tenant scope. Destructive endpoints (delete, suspend, etc.) only affect your tenant's data.
The sandbox runs at relaxed limits — sufficient for exploration. Production deployments are tunable per engagement.
The Swagger UI doc and OpenAPI JSON at cleen-prod-api.azurewebsites.net. Both update on every API deploy.
Yes — that's CleenUI. Book a 30-minute architecture review and we'll scope a license.
The Postman collection lets you see the API surface. The Full-Stack license gives you the C# source, the database schema, the modules, and the architect to integrate it.