Skip to main content

Screening – Added

A new endpoint returns the document state of every match in a batch in one call. For each match that has at least one document, it returns the number of documents provided, still in progress, failed and virus-detected, so a client can check the documents on every hit without requesting each match individually. Matches with no documents are not returned, and only match documents are counted (entity documents are not). The optional onlyBlocking query parameter (default false) limits the response to matches that have a document still in progress, failed or virus-detected, which keeps it small for very large batches. The endpoint is available to tenants where the feature is enabled and returns 403 otherwise.

The existing endpoint that returns the document state of every entity in a batch now also reports the number of failed and virus-detected documents for each entity.

A document counts as failed when its upload or processing did not complete, as virus-detected when the virus scan found malware in it, and as in progress while it is still being uploaded or scanned.

Lookup – Added

New optional tags property (list of strings) on lookup (reference data list) versions, so lists can be categorised (for example KYC). Tags are accepted when creating or updating a lookup version and are returned on full lookup version responses. When tags is omitted or null on an update, the existing tags are kept; when a new version is created without tags, it inherits the tags of the active version; sending [] clears them. Tags are trimmed and de-duplicated (case-insensitively) before being stored. Each version can have at most 20 tags, each 1–50 characters of letters, digits, hyphens and spaces; invalid tags return 400 Bad Request. Existing lookups return an empty list, so this change is fully backward compatible. (AB#554576)

Screening – Updated

Entity responses now include a matchSummary: a per-provider breakdown of the entity's matches by resolution status (unresolved, match, no match). Clients can render batch-level summaries from a single entity list call instead of fetching every entity's matches individually. Counts are per provider, so a client that needs an entity-level total sums across the providers it cares about.

A new endpoint returns the document state of every entity in a batch in one call: for each entity, the number of documents provided and the number still in progress. Entities with no documents are included with zero counts, and only entity documents are counted (match documents are not).

Screening – Added

Virtual documents are now available for Screening in all tenants. Two new endpoints let you attach a document to a screening entity or to an individual match by supplying a link to a file hosted outside Fenergo's storage, instead of uploading the file through the signed-URL flow. The link must be an absolute https:// URL.

The document list endpoints for entities and matches now return a documentUrl field. It is populated for virtual documents and null for documents uploaded through the signed-URL flow.

Policy – Added

Added normalized variants of the v4 entity policy fields evaluate endpoint, for collection data groups with many items. Each collection data group returns every unique evaluated field once in its evaluatedFields list, and each item carries only an ordered evaluatedFieldRefs list of integer indices into that list, reducing payload size. To rebuild an item, resolve each index against the list in order. Indices are assigned per response and are not stable across requests.

The normalized endpoint takes the same request as the existing endpoint and returns the same evaluations; only the shape of the collection data groups differs. The existing endpoint is unchanged.

The read-only/normalized endpoint returns a slimmer field shape intended for read-only and display scenarios: only the single fields and collection data groups, each with the properties needed for display. Values evaluation is always skipped, validation errors are not returned, and access layers filtering is always applied, so these options are not part of the request.

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