WORLD CHECK ONE API TIME OUTS

Sara.Williams
Sara.Williams LSEG
in World-Check One

Observing no response whatsoever within a 10 second timeout. Should it be set for a longer time out? We previously had a
longer timeout (I forget whether it was 30 or 60 seconds) and reduced it to
improve the student experience in the case of a timeout -- and we didn't see
much difference in incidence rate of timeouts when we reduced the timeout,
which suggests that timeout is just a symptom of failure, rather than being the
root issue. Here is an example:

Here's debug output from me (successfully) retrying a
request that previously timed out:

===== REQUEST =====

Request: POST http://rms-world-check-one-api.thomsonreuters.com:443/v1/cases/screeningRequest

Request headers:

content-type: application/json

authorization: Signature
keyId="<redacted>",algorithm="hmac-sha256",headers="(request-target)
host date content-type
content-length",signature="I00IJdJSBSFfJbCuyilxsiCBJqhqgkxgIeLITI0vmrM="

date: Tue, 04 Dec 2018 18:54:00
GMT

connection: close

POST Data:
{"groupId":"0a3687c3-6359-1ee7-98e3-243c0000073c","entityType":"INDIVIDUAL","providerTypes":["WATCHLIST"],"name":"Maya
Lein","customFields":[{"typeId":"0a3687c6-64e5-1d18-9949-2253000010b5","value":"6556680064729088"}],"secondaryFields":[{"typeId":"SFCT_3","value":"DEU"}]}

===== RESPONSE =====

Code: 200

Headers

x-application-context:
"application"

cache-control: "no-cache,
no-store, max-age=0, must-revalidate"

pragma: "no-cache"

expires: "0"

x-xss-protection: "1;
mode=block"

x-frame-options:
"DENY"

x-content-type-options:
"nosniff"

date: "Tue, 04 Dec 2018
18:54:00 GMT"

content-type:
"application/json;charset=UTF-8"

transfer-encoding:
"chunked"

server:
"\"\""

connection: "close"

Body:
{"caseId":"3c3a4448-1105-46ca-b345-4ad28f366583","results":[]}

Tagged:

Best Answer

Answers

Categories