@rnana

Hi,

I checked the logs to see if the request is hitting our servers and I can confirm that the last request that hit our servers from your keys was on 21st December and the 401 that you observed yesterday didn't reach our servers.

we suspect there is still an issue with the CORS on your side which may be blocking certain requests, can you check the code for any CORS issue?

Also, I would like you to hit a request bin target whose details I will send across via email so that I can capture all the details about the request that you're sending to check if there are any issues.

Email to follow.

@rnana

Can you share the complete request and response header of the failed API call so that we can investigate it further?

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. You should ensure a correctly synchronized clock is used to generate request timestamps.
• Incorrect JSON payload formation at your end that can cause 401 response.

@Mehran Khan thanks for your response.

API_KEY_VALUE and API_KEY_VALUE are replaced by their value. these ones are hidden here for security reasons.

@Mehran Khan

Kindly find some screenshots: request and response header