TM Observability – Added
Fetch batch transaction information either by batch IDs or by date range.
Fetch batch transaction information either by batch IDs or by date range.
Added property ForbiddenEntityDrafts to SearchEntityDrafts response.
/entitydataquery/api/v2/entity/search-entity-draftsThe batch upload endpoint now accepts transactions that contain an unknown entity, instead of rejecting them.
Added DriversLicense, SocialSecurityNumber (SSN), and EmployerIdentificationNumber (EIN) 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.
Updated Risk Assessment models to contain ThresholdColor.
/riskquery/api/risk-assessment/riskquery/api/risk-assessment/{taskId}/riskquery/api/risk-assessment/taskResults/riskquery/api/risk-assessment/related-parties/{taskId:guid}/riskquery/api/risk-assessment/related-parties/{taskId:guid}/entity/{entityId:guid}Added new property Thresholds to RiskFactorGroupRiskAssessmentViewModelDto.
/riskquery/api/risk-model/riskquery/api/risk-model/{id}/riskquery/api/risk-model/{id}/version/{versionNumber}/riskcommand/api/risk-model/riskcommand/api/risk-model/{id}/riskcommand/api/risk-model/{id}Added requirement for If-None-Match header in endpoint request,
to ensure rejecting conflicting uploads under the same url.
/api/transactions/batch/generate-upload-urlUpdated ThresholdDto and RiskFactorGroupThresholdDto models to include ThresholdColor property.
/riskquery/api/threshold-model/riskquery/api/threshold-model/{id:guid}/riskquery/api/threshold-model/{id:guid}/version/{versionNumber:int}/riskcommand/api/threshold-model/riskcommand/api/threshold-model/{id:guid}/riskcommand/api/threshold-model/{id:guid}/riskquery/api/risk-model/riskquery/api/risk-model/{id}/riskquery/api/risk-model/{id}/version/{versionNumber}/riskcommand/api/risk-model/riskcommand/api/risk-model/{id}/riskcommand/api/risk-model/{id}New "AutonomyLevel" property added to BatchMetadataDto. Depending on the value, the matches will be auto-resolved using an AI Agent when they come back from the provider, and auto-close the Screening Results task. Possible values: Manual (default), Semi-Autonomous, Fully Autonomous
New "LastActionedBy" property added to MatchDto. This new property will be used to identify who actioned the resolution of the match, i.e KYRA:Screen, Screening Provider or manually by user (manuallyByUser@test.com).
Improved the Transaction Batch documentation and OpenAPI specification to better reflect request/response formats and to improve generated API reference rendering.