DecisionManager

Documentation

The API, without an account.

No email wall and no lead form. If the API does not convince you, a gated PDF will not either.

API module map

Four backend services, one workspace model, one auth model. Ports below are the local defaults the extension, Studio workspaces, and this page use.

API module map
ServicePortPrefixOwns
platform:8081/api/auth · /api/me · /api/workspaces · /api/trial · /scim/v2identity, tenancy, trial lifecycle, OpenAPI document
decision manager:8082/api/managerauthoring, governance, testing, ODM migration
decision server:8083/api/serverdeployment, execution, warehouse
admin:8084/api/adminmembers, API keys, webhooks, audit, quotas

Blue/green traffic mutation (PUT …/traffic, POST …/rollback) is served by decision manager on :8082, not decision server on :8083. Health live/ready answers on every service.

Browser consoles

Each console talks to its API module over the same governed repository. All three consoles are included in every plan — product pages describe the surface; open the console to use it.

Decision Manager

API :8082 · UI :3000

Where business and engineering design, test, and govern decision logic.

Decision Server

API :8083 · UI :3001

The hot path: deploy, execute, and measure decisions in production.

IDE vs browser consoles

Decision Manager and Decision Server each have a browser console. Developers who prefer an editor use the VS Code extension against the same Manager and Server APIs — one repository, two surfaces. Neither surface replaces the other.

Decision Manager (browser)

console · manager :8082

Authoring and governance for business and engineering together: decision-table grid, action rules, ruleflow canvas, vocabulary, review and promotion. The surface a policy owner opens in a meeting.

Decision Server (browser)

console · runtime :8083

Operations: deploy published versions, execute against an environment, read execution history and warehouse health. Not an authoring IDE — the console an operator keeps open.

VS Code extension (IDE)

editor · platform + manager + runtime + admin

The developer half: repository explorer, BAL/JSON with vocabulary-driven LSP, decision trace, Test Explorer, governed deploy and Git export. Install from the measured .vsix — same four API modules, no second source of truth.

Which surface for which task
TaskBrowser consoleVS Code IDE
Edit a decision table with a gridManager — primaryJSON / dmrule in the editor
BAL completion & live validationManager in-console editorLSP against Manager vocabulary APIs
Submit / approve / publishManager governance UIGovernance view (same lifecycle)
Deploy to an environmentServer consoleDeploy commands → runtime API
Ops: history, warehouse, slotsServer console — primaryNot the focus of the extension
Git export / multi-file diffPull/export helpers in ManagerNative VS Code diff & Git

Compared with IBM ODM's Eclipse Rule Designer + Decision Center + RES console split, the browser consoles cover Center/RES roles and the VS Code extension is the designer-for-developers path — without requiring an Eclipse install. Download the VS Code extension

Trial lifecycleplatform :8081

Create a trial, read its entitlements, extend it, convert it, cancel it, and take your data out. Cancel and export are ordinary endpoints, not a support ticket.

Trial lifecycle
POST/api/trial/signup
GET/api/trial/tiers
GET/api/trial/:wid
POST/api/trial/:wid/extend
POST/api/trial/:wid/convert
POST/api/trial/:wid/cancel
GET/api/trial/:wid/export

ODM migrationmanager :8082

Upload an ODM export, analyse it against your workspace for the gap report, then commit the rules that translated. Analyse is non-destructive: nothing is written until you commit.

ODM migration
POST/api/manager/workspaces/:wid/odm/services
POST/api/manager/workspaces/:wid/odm/analyze
POST/api/manager/workspaces/:wid/odm/commit

Executionruntime :8083

Execute a deployed decision service against an environment and get the decision, the matched rules and the step count back.

Execution
POST/api/server/services/:sid/execute
The API, without an account.
OpenAPI

OpenAPI

The full generated specification is served by the platform.

GET /api/openapi.json

platform :8081

Known issue, stated here rather than found by you

POST /api/server/services/:sid/execute currently returns 500 INTERNAL_DB on this build: a SUM() over a bigint column returns NUMERIC and is decoded as i64 in backend/crates/runtime/src/api.rs. A fix is with the runtime team. We would rather you read that here than hit it in your first five minutes.