We are getting a 401 code on https://rms-world-check-one-api-pilot.thomsonreuters.com/v1/groups This was still working the last week of December and we have not made any code changes.
For a deeper look into our World Check One API, look into:
1
●0 ●0 ●1
We are getting a 401 code on https://rms-world-check-one-api-pilot.thomsonreuters.com/v1/groups This was still working the last week of December and we have not made any code changes.
Hi,
Thank you for your participation in the forum.
Is the reply below satisfactory in answering your question?
If yes please click the 'Accept' text next to the most appropriate reply. This will guide all community members who have a similar question.
Otherwise please post again offering further insight into your question.
Thanks,
AHS
Hi,
Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.
Thanks,
AHS
2.4k
●6 ●5 ●6
Hi,
401 errors occur because the request has failed an authorization check. This can happen for a variety of reasons, such as
- An invalid or expired API key,
- An invalid HMAC signature.
- Request timing issue/problem with the Date header value. In this scenario, you should ensure a correctly synchronized clock with NTP or the GMT clock is used to generate request timestamps.
- Incorrect JSON payload formation at your end that can cause a 401 response.
Can you please share the complete request and response for the failed API call so that we can investigate this further?
Thanks,
Mehran Khan
