HSBC - Urgent Issue in Production Environment (404 NotFound)

Unknown

Hi, We are experiencing issues with the screening service since today, these are the details of the problem:

Parameters used

The URL for API Production is: rms-world-check-one-api.thomsonreuters.com

API Key: 0b7990d5-e938-46fd-9608-6c81f924456b

API Secret: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Application logs

address: /v1/groups

Authorization: Signature keyId="0b7990d5-e938-46fd-9608-6c81f924456b",algorithm="hmac-sha256",headers="(request-target) host date",signature="V+ZiFKQ7vKTOqcuHygMXIpWENZJTldJdBx8b6rLIEEg="

The error received:

404 Not Found.

The full adreess is:

rms-world-check-one-api.thomsonreuters.com/v1/groups and we made a get to obtain the ID, this same application in our development environment works fine with the Pilot URL.

As this is the first time that we need to interact with you for production issues, could you please specify if you need any further information in order to help us to solve it?

Appreciate your response as soon as possible as this is stopping our customer onboarding service.

Kind regards.

emma.farmer

Hi @jcgarcia

It looks like on 31 Oct, the Client Admin deleted the user to which the API key and secret were assigned so this is why they no longer work. Please let me know via email which User's API key and secret you wish to use.

Many thanks
Emma

emma.farmer

Hi @jcgarcia

I will email you separately as it appears you have the incorrect API key.

Thanks

Emma

Unknown

the API Key: 0b7990d5-e938-46fd-9608-6c81f924456b was given by Brian Bourgalt

At 4th October.

Thanks.

Unknown

Hi We still have errors, we see now in our production environment that sometimes the error “404 not found” appairs and sometimes not.

For example, this case:
/v1/cases/0a3687d0-5fe4-1953-97fb-9ffc00009215/results
Return 404 not found

And this one...
/v1/cases/0a3687c4-5fa9-14ff-97fb-a071001113b8/results
Return OK, with information…

[{"resultId":"0a3687c6-5fa8-1166-97fb-a07300c11561","referenceId":"e_tr_wci_2285082","matchStrength":"WEAK","matchedTerm":"Robert M","submittedTerm":"ROBERTO JUSTINIANO MALDONADO ","matchedNameType":"LOW_QUALITY_AKA","secondaryFieldResults":[{"field":{"typeId":"SFCT_1","value":"MALE","dateTimeValue":null},"typeId":"SFCT_1","submittedValue":"MALE","submittedDateTimeValue":null,"matchedValue":"MALE","matchedDateTimeValue":null,"fieldResult":"MATCHED"},{"field":{"typeId":"SFCT_2","value":null,"dateTimeValue":null},"typeId":"SFCT_2","submittedValue":null,"submittedDateTimeValue":"1972-11-19","matchedValue":null,"matchedDateTimeValue":null,"fieldResult":"UNKNOWN"},{"field":{"typeId":"SFCT_3","value":"AUT","dateTimeValue":null},"typeId":"SFCT_3","submittedValue":"ARG","submittedDateTimeValue":null,"matchedValue":"AUT","matchedDateTimeValue":null,"fieldResult":"NOT_MATCHED"},{"field":{"type

We don’t understand what happened, why for some cases works fine and with other cases not.

Could you help us please.

Thanks

shilpi.saha

jcgarcia,

Can you please provide us the Case body whenever you get 404 error.May be will be investigate further what's the exact issue.

Thanks,

Shilpi

Unknown

Please discard the last message, we had wrong the url in one server.

Thanks.