@epilot/integration-toolkit-client 1.1.0 → 1.1.2

package/dist/openapi.d.ts

@@ -797,6 +797,11 @@ declare namespace Components {
              * evt-2025-05-01-12345-create-bp
              */
             deduplication_id?: string; // ^[a-zA-Z0-9_-]+$
+            /**
+             * Resolved use case ID for the inbound event. Null when no use case matched or for events ingested before this field was introduced. Server-populated only — ignored if supplied on inbound requests.
+             *
+             */
+            use_case_id?: string | null;
         }
         export type ErpEventV3 = {
             /**
@@ -1381,6 +1386,11 @@ declare namespace Components {
              * Field to group the breakdown by
              */
             group_by?: "use_case_id" | "use_case_type" | "level" | "code" | "date";
+            /**
+             * Data source for the stats. "monitoring" (default) aggregates processed events from erp_monitoring_v2 — this counts every event produced throughout the processing tree (fan-out children, post-actions, relation resolutions, etc.). "incoming" counts only the initial inbound events actually received (distinct event_id from erp_incoming_events); only group_by=use_case_id is supported and status/level breakdown is not available for this source (success/error/warning/skipped counts are returned as 0).
+             *
+             */
+            source?: "monitoring" | "incoming";
         }
         export interface GetMonitoringTimeSeriesRequest {
             /**
@@ -2929,6 +2939,10 @@ declare namespace Components {
              * Filter by event name (alias for object_type)
              */
             event_name?: string;
+            /**
+             * Filter by use case ID
+             */
+            use_case_id?: string;
             /**
              * Maximum number of results to return
              * example:

package/dist/openapi.json

@@ -2,7 +2,7 @@
   "openapi": "3.0.3",
   "info": {
     "title": "Integration Toolkit API",
-    "version": "1.0.11",
+    "version": "1.0.12",
     "description": "API for integrating with external systems in a standardised way."
   },
   "tags": [
@@ -3144,6 +3144,12 @@
             "maxLength": 255,
             "description": "Optional unique identifier for idempotency - prevents duplicate processing of the same event within 24 hours in context of the same integration. Must contain only alphanumeric characters, hyphens, and underscores.\n",
             "example": "evt-2025-05-01-12345-create-bp"
+          },
+          "use_case_id": {
+            "type": "string",
+            "nullable": true,
+            "readOnly": true,
+            "description": "Resolved use case ID for the inbound event. Null when no use case matched or for events ingested before this field was introduced. Server-populated only — ignored if supplied on inbound requests.\n"
           }
         }
       },
@@ -6870,6 +6876,11 @@
             "type": "string",
             "description": "Filter by event name (alias for object_type)"
           },
+          "use_case_id": {
+            "type": "string",
+            "minLength": 1,
+            "description": "Filter by use case ID"
+          },
           "limit": {
             "type": "integer",
             "description": "Maximum number of results to return",
@@ -7826,6 +7837,15 @@
               "date"
             ],
             "description": "Field to group the breakdown by"
+          },
+          "source": {
+            "type": "string",
+            "enum": [
+              "monitoring",
+              "incoming"
+            ],
+            "default": "monitoring",
+            "description": "Data source for the stats. \"monitoring\" (default) aggregates processed events from erp_monitoring_v2 — this counts every event produced throughout the processing tree (fan-out children, post-actions, relation resolutions, etc.). \"incoming\" counts only the initial inbound events actually received (distinct event_id from erp_incoming_events); only group_by=use_case_id is supported and status/level breakdown is not available for this source (success/error/warning/skipped counts are returned as 0).\n"
           }
         }
       },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@epilot/integration-toolkit-client",
-  "version": "1.1.0",
+  "version": "1.1.2",
   "description": "Client library for epilot Integration Toolkit API",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",