Skip to main content

Screening – Added

Screening now supports uploading, reusing, and deleting documents at both the entity level and the individual match level within a batch, using the same upload-URL/reuse pattern as other document flows in the platform. New materiality endpoints let users escalate and de-escalate a materiality task on an entity, trigger aggregate entity materiality calculation for a batch, and retrieve the full materiality assessment history for an entity.

A number of existing Batch, Entity, and Match endpoints have also been extended with new fields to support this materiality workflow: journey type and main legal entity on batch creation and retrieval, entity-level materiality assessment/escalation/impacted-client details, and match-level classification data and last-actioned-by information.

Entity-Data – Changed

The partial-properties endpoint is now unconditionally available to all callers. Request/response schema is unchanged.

Affected Endpoints

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

Entity-Data – Added

New endpoint returning a page of draft entity/journey membership ({ EntityId, EntityDraftId }) per matching draft, for callers that need journey draft membership without the full draft payload. Same authorization/filtering rules as the existing search endpoint. Request gains an optional page options object (page size, pagination token, sort order); response is now a page of items plus a pagination token instead of a bare array. Omitting page options defaults to a page size of 100; page size accepts 1-500.

Affected Endpoints

  • POST /entitydataquery/api/v2/drafts-in-scope/search-entity-drafts-light

Entity-Data – Changed

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