Ventoo Case Management provides twelve API pages for integration with external systems (e.g. external registration systems, diagnostic tools, or custom portals).
Endpoint
The APIs follow the Business Central standard for custom APIs:
|
Attribute |
Value |
|---|---|
|
Publisher |
|
|
Group |
|
|
Version |
|
The base path is therefore:
/api/ventoo/caseManagement/v1.0/<entitySet>
Example: /api/ventoo/caseManagement/v1.0/cases
Authentication and calls work as with all BC APIs (OAuth). Access is subject to the app's BC permission sets.
Available entities
|
Entity set |
Entity |
Methods |
|---|---|---|
|
|
Case |
GET, POST, PATCH |
|
|
Engagement |
GET, POST, PATCH |
|
|
Scope |
GET, POST, PATCH |
|
|
Scope Schema |
GET, POST, PATCH |
|
|
Activity |
GET, POST, PATCH |
|
|
Task |
GET, POST, PATCH |
|
|
Party |
GET, POST, PATCH |
|
|
Relationship |
GET, POST, PATCH |
|
|
Role |
GET, POST, PATCH |
|
|
Attribute |
GET (read-only) |
|
|
Attribute Value |
GET, POST, PATCH |
|
|
Case Ledger Entry |
GET (read-only) |
The exact methods supported per page follow from their settings (e.g. delete is disabled on several pages;
attributesandcaseLedgerEntriesare read-only). Case ledger entries are a posted ledger and therefore read-only.
Typical use cases
-
External case creation – an external registration system creates cases with parties and scope directly via API.
-
Time and result feedback – a diagnostic/third-party tool writes activities and attribute values back onto existing cases.
-
Evaluation – case ledger entries are read out to present metrics in an external system.
For tenant-specific integrations, the app additionally offers integration events at key points (case creation, status change, posting) to which tenant-specific extensions can attach.