Skip to main content

Screening – Added

A new endpoint is available to evaluate the Screening Expiry snapshot for a journey. Given a journey ID and a list of process IDs, it returns the expiry status of each process's active screening batch, broken down by provider.

External Authentication – Added

The endpointCertificate object now accepts an optional validationMode property that controls how the server certificate of your endpoint is validated for mTLS. Supported values are PinLeafThumbprint (default when omitted, existing behaviour) and SignerChainValidationOnly. The same property applies to oAuthConfiguration.clientCredentialsConfig.endpointCertificate, and is returned when a configuration is retrieved. Existing configurations are unaffected.

Document Management – Changed

Direct callers of the Document Management Command API v2 could get a false "Entity DocumentModel with id {id} not found" error on these endpoints when acting on a document whose real entity type is Screening (or any other type with no dedicated mirrored route) — entity type was previously derived only from the route name (product/deal/else Entity). Each endpoint now accepts an optional documentEntityType query parameter; when supplied, it is used to resolve the document's entity type instead of the route name. Omitting the parameter reproduces the previous behaviour exactly, so this is fully backward compatible. (AB#552592)

Affected Endpoints​

  • PUT /documentmanagementcommand/api/v2/documentmanagement/{id}
  • DELETE /documentmanagementcommand/api/v2/documentmanagement/{id}
  • PUT /documentmanagementcommand/api/v2/documentmanagement/{id}/access-layers
  • PUT /documentmanagementcommand/api/v2/documentmanagement/{id}/clone
  • PUT /documentmanagementcommand/api/v2/documentmanagement/{id}/requirement-ids
  • PUT /documentmanagementcommand/api/v2/documentmanagement/{id}/datakey
  • PUT /documentmanagementcommand/api/v2/documentmanagement/{id}/updateDocumentUploadedByUserName
  • PUT /documentmanagementcommand/api/v2/documentmanagement/error/{id}
  • PUT /documentmanagementcommand/api/v2/documentmanagement/custom-error/{id}

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