I am assisting my customer with migrating from the World-Check One API v1 to v3. To support this, I’m preparing a Postman environment, sending sample requests, and reviewing the responses. The goal is to demonstrate the differences between the two versions and help the customer better understand the changes. While…
Hello We have successfully implemented and tested WorldCheckOne integration in our development stage. HMAC-Authorization worked perfectly fine. We are now testing on the acceptance stage at our customer, where all requests are routed through an Enterprise Service Gateway. This means that our request goes to…
As per LSEG World-Check One API Security Authorization mention below Authorization: Signature keyId="{API-KEY}",algorithm="hmac-sha256", headers="(request-target) host date content-type content-length", signature="{BASE64-HMAC-VALUE}" can you please help how to give in Postman
Dear Team, I am trying to create / screen a case via C# app, Though I am getting the correct signature and authentication. Still I am getting "Unauthorized" response. Where as via Postman request i am getting correct response and case created successfully Can you help me resolving the issue ?
Hello, We are migrating from WC1 V1 to V3, and so far we have been iterating through OGS updates by specifying updatedDate in the query field and sorting by updateDate, for example: { "pagination": { "currentPage": 1, "itemsPerPage": 20 }, "sort": [ { "columnName": "updateDate", "order": "ASCENDING" } ], "query":…
Hello, We use World-Check v2 API in order to implement ongoing screening. Recently we noticed that method /cases/{caseSystemId}/ongoingScreening returns HTTP 423 Locked for some cases, but this response code is missing from the API docs. I tried reproducing it and got HTTP 204 instead, so the issue seems to be sporadic.…
Hi there. I want to get response of the endpoint cases/ongoing-screening-updates. But I couldn't get screening results by OGS screening. I used WCA API V3. I called api like bellow. ``` {{protocol}}{{gateway-host}}{{gateway-url}}cases/ongoing-screening-updates { "filter":…
We have some questions regarding data retrieval from Sayari(UBO) via API. Our client wants to know whether this UBO API has below these functions 1.Alerts for shareholder changes 2.Alerts for changes in ownership ratios 3.Alerts for company name changes My understanding is that we can not based on below documents…
I have Media Check enabled in WC1 environment, but when I call API I receive this error:
It looks like you're new here. Sign in or register to get started.
