Retrieving detailed entities/profile information

👉
Navigation

Overview

Terminology

Conceptual differences

Use cases

API authentication.

Onboarding and screening a customer.

Checking for hits/profiles.

Retrieving detailed entity/profile information.

💡
Use case: Retrieving detailed entities/profile information for a customer's hits

At the time of onboarding a customer:

Current solution	ComplyAdvantage Mesh
Parse the hits object in the POST /searches response	• Retrieve alert_identifier from GET workflows/{workflow_instance_identifier} or WORKFLOW_COMPLETED webhook • Fetch the risks within the alert using GET alerts/{alert_identifier}/risks
API reference	API reference – get workflow status API reference – webhooks API reference – get risks with an alert

At any time after onboarding a customer:

Current solution	ComplyAdvantage Mesh
GET /searches/{id}/entities/view](https://doc	• Get the case_identifier using: GET customers/{customer_identifier}/cases • Get the alert identifiers for the case: GET cases/{case_identifier}/alerts • Get the risks within the alert: GET alerts/{alert_identifier}/risks
API reference	API reference – get customer's cases API reference – get alerts for a case API reference – get risks with an alert