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.

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.

The Agency Product Verified endpoint now accepts an optional journeyId query parameter to check whether all associations for a completed journey are verified.

Added new endpoints for Legal Hold management.

Legal hold allows placing an entity under a legal hold, which prevents data deletion processes from proceeding.

Extended the requirement set retrieval API to support a configurable limit on the number of versions returned per jurisdiction.

New query parameter versionsLimit (optional): An integer to specify the maximum number of versions per jurisdiction. If not provided, it returns all.

The batch transaction response status now includes two additional intermediate values:

• pending_ingestion
• ingestion_in_progress

This applies to batch transaction status responses in the Observability API.

Poll the execution status summary from the Observability API using the execution_id. This works for both tenants using either the Rule Rerun API or the Rule Execution API endpoints

• GET /api/v1/rules/execution?execution_id={execution_id}

Poll the rule execution status summary using the execution_id retrieved only when using the Rule Execution API endpoint

• GET /api/rules/status/{execution_id}

The previously deprecated failed_transaction_modification_ids and progress_percentage fields are no longer returned in the batch status response.

The Rule Schedule API provides visibility into rules execution schedule.

• POST /api/rules/schedule