2026-10-14 Integration Toolkit API
Action needed code on monitoring events, associated events, and trace spans is no longer always a string, so consumers must handle other value types
Action needed ERP update submissions on the /v1, /v2, and /v3 erp/updates/events endpoints now return a new optional correlation_close field, v3 events and correlations report omitted entities through a new optional entities_omitted field, and monitoring events, associated events, and trace spans can now report the new PROCESSING_STATE_LIMIT code, so consumers must be prepared for this additional value
New New GET /v3/erp/updates/events, GET /v3/erp/updates/events/{event_id}, and GET /v3/erp/updates/correlations endpoints were added for tracking submitted ERP update events and their correlations, including whether a correlation is complete and its errors_total
New New POST /v2/integrations/{integrationId}/monitoring/runs/completion endpoint was added for reporting the completion of a monitoring run
Changed ERP updates can now be processed interactively: POST /v3/erp/updates/events accepts new optional interactive, events[].interactive, and correlation_complete fields, use cases accept a new optional configuration.interactive field, and the /v1, /v2, and /v3 erp/updates/events endpoints now return a correlation_id together with each result's interactive flag and lane
Changed group_id and events[].group_id on POST /v3/erp/updates/events must now be non-empty and contain only printable characters without spaces