Platform API and Partner API Release Notes for September 2026

Platform Release

September 12 2026

Platform API and Partner API features, enhancements, and fixes are not in the runtime release.

New Features

• Introduced JMS v2 as an Early Access connector in the Trading Partner Framework. JMS can be configured directly in a Trading Partner component or shared via a Shared Communication Channel component. TradingPartner and SharedCommunicationChannel APIs support create, read, update, query, and delete of components that include the JMS configuration options. (B2B-5320)

Enhancements

• Extended the Audit Log Query (SOAP and REST) API to support additional query operators: LIKE, NOT_EQUALS, IS_NULL, IS_NOT_NULL, STARTS_WITH, IN, and NOT_IN, along with existing operators EQUALS, BETWEEN, GREATER_THAN, GREATER_THAN_OR_EQUAL, and LESS_THAN_OR_EQUAL. (PS-11093)

• Added a createdDate field to the IntegrationPackInstance REST and GraphQL APIs, so you can sort and identify installed integration packs by when they were created. (INT-17341)

• Added executionWorkerId and clusterNodeId query filters to the ExecutionRecord API, so you can troubleshoot issues with specific execution workers or cluster nodes. (RUN-6895)

Fixes

• Resolved an issue where the Audit Log Query REST API always sorted results by date in ascending order, regardless of the requested sort field. You can now sort by date, userId, action, source, modifier, or level, in ascending or descending order using QuerySort. (PS-13811)

• Resolved an issue where the Audit Log Query REST API returned a generic server error for invalid query requests. The API now returns a descriptive, actionable error message. (PS-11093)

  note

  You can only retrieve one year of audit log data using the Audit Log Query (SOAP and REST) API.