Entity Data – Changed
This endpoint is marked as obsolete but will continue to be supported with no planned termination date. However, its usage is not recommended as it does not support full field-level validation.
This endpoint is marked as obsolete but will continue to be supported with no planned termination date. However, its usage is not recommended as it does not support full field-level validation.
Update BatchExternalIds to use their own model (BatchExternalId instead of ExternalId), as it does not make sense for a BatchExternalId to have EntityAliasId since BatchExternalId is specifically related to the batch, not any of its entities. This should not affect any clients as Alias Screening has not been enabled yet.
Added fields to support implementation of Alias Screening. There are no breaking changes here, so adapter implementations will continue to work as normal without the need of making any change.
Extend configuration to support capturing a list of data keys for document expiry data fields
Added PassportNumber to SearchCriteria in batch and to SecondaryIdentifiers in configuration. Right now it's only supported for LexisNexis and any custom providers that want to implement it.
Changed Validation behaviour for Document Requirement Update (Waiving)
Adjusted endpoint configuration in order to support additional document metadata columns
Added optional properties to role configuration:
getEntitiesPagedList has additional validation for the Pager.From and SearchAfter params. Only one can be used at a time.
If both are provided, the request will return a 400 Bad Request error.
Updated the max teams limit to 300, max access layers to 2000