Screening with exits case ID

duong.nguyen

Dears,

I have trouble when call API,

Step 1 : Screening with customer NVD_test_abc and return case id
= "6eeffbab-c313-47e6-92b8-1c8e71739177"

Step 2: Rescreening customer NVD_test_abc with case id =
"6eeffbab-c313-47e6-92b8-1c8e71739177" like below

-> Show error

cause:"Case
IDs must be unique within the same client." and
error:"CASE_ID_EXISTS"

{

"groupId":"{{group-id}}",

"caseId":
"6eeffbab-c313-47e6-92b8-1c8e71739177",

"entityType": "INDIVIDUAL",

"providerTypes": [

"WATCHLIST"

"name": "NVD_test_abc",

"secondaryFields":[.......

"customFields": []

}

Thanks!

Find more posts tagged with

world-check-one

world-check

Accepted answers

Prabhjyot

@duong.nguyen,

Thank you for your query.

For rescreening a case, client will have to use the API call
– “SEQ-screen-async: Screen a case” and would need the case-system-id of the
saved case.

Hope this helps.

All comments

Prabhjyot

@duong.nguyen,

Thank you for your query.

For rescreening a case, client will have to use the API call
– “SEQ-screen-async: Screen a case” and would need the case-system-id of the
saved case.

Hope this helps.

duong.nguyen

Dear Prabhjyot.Mandla,

Do
you have any API using SYNC instead of ASYNC,

Note: I know
how to use the API call “SEQ-screen-async: Screen a case” but we need result
immediately when API call.

Thank you for your reply!

Chris.Lee1

Hi Nguyen,

Thank you for your query, please see below, currently WC1 API has 4 Sync POST for your reference.

duong.nguyen

Dear Chris Lee,

Thanks for your reply, but I mean do you have any API using SYNC instead of ASYNC for re-screening using exist case id like problem above?

Thanks!

Chris.Lee1

Hi Nguyen,

Thanks for your query, i am afraid re-screening can only be done asynchronously.

EXPLORE OUR SITES