For a deeper look into our World Check One API, look into:

Overview |  Quickstart |  Documentation |  Downloads

question

Upvotes
Accepted
1 0 0 0

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.

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.

world-checkworld-check-oneerror-401
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

Upvotes
Accepted
2.4k 5 5 5

@Raini-Kevin

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

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.