The Batch Upload API is now subject to per-tenant rate limits.

The Transaction API is now subject to a per-tenant rate limit.

The maximum number of EntityIds accepted per request is raised from 10 to 100. Requests above the new limit are still rejected with a validation error. Response shape is unchanged.

Affected Endpoints​

• POST /entitydataquery/api/v2/entity/drafts/names

New V3 Entity endpoints are now available. These replace the existing V1/V2 entity endpoints and introduce two key improvements: support for multiple addresses per entity in SearchCriteria, and per-configuration-set targeting when toggling Ongoing Screening.

Additionally, the ConfigurationSetId field is now exposed in the Ongoing Screening results callback, enabling adapters to identify which configuration set a screening result belongs to.

New endpoint that returns a named subset of an entity draft's properties for up to 10 drafts in a single request. Each result carries the draft's id, type, and only the top-level property keys named in the request. Requested keys that don't exist on a draft are omitted, and drafts that don't exist or that the caller cannot access are omitted from the response.

Affected Endpoints​

• POST /entitydataquery/api/v2/entity/drafts/partial-properties

GraphQL responses — including auth-denied ones — from both EntityData subgraph hosts now include the Platform security headers Strict-Transport-Security and Content-Security-Policy.

Affected Endpoints​

• POST /graphql

Entity draft/entity update validation now honours Policy ExternalDataGroupProvider rules for data group fields when creating external adapter validation requests. Request/response schema is unchanged; affected command endpoints now correctly reject invalid data group rows returned by the external provider.

Affected Endpoints​

• All entity draft/entity update command endpoints that trigger external data group validation (validation behaviour only — no schema change).

Entity draft/entity update validation now sends data group fields to external adapter providers as grouped requests (one request per collection row per provider) instead of individual single-field requests. Request/response schema is unchanged; validation error messages returned to callers are unaffected.

Affected Endpoints​

• All entity draft/entity update command endpoints that trigger external data group validation (validation behaviour only — no schema change).

Two new SLA Event Notifications have been added to the journey feed:

• journey:slaapproachingdue — published every 10 minutes when one or more SLA instances reach their Approaching Due threshold.
• journey:slapastdue — published every 5 minutes when one or more SLA instances pass their Committed Date without being completed.

Both events apply to Journey-, Stage-, and Task-level SLAs and are published as collection events. They are off by default per Journey Schema and must be enabled via the Journey Configuration modal in Journey Builder before any notifications will be published.

Please refer to Notifications Event Registry for sample payloads.

New endpoint that returns the entity id, draft id (when applicable), type, display name, and aggregate version for each requested entity within a journey context. Uses the journey's draft when present, falling back to the verified entity record otherwise. Only accessible records are returned; inaccessible and forbidden records are silently omitted.

Affected Endpoints​

• POST /entitydataquery/api/v2/entity/drafts/names