Start a new topic

POST problem with authentication

GET is  working fine but with POST I have only failed authentication

I have problem with specification for example :


signature is derived from:


POST request :


So url is only:

and payload is ?  api_key=API_KEY&name=NAME&request_timepstamp=EPOCH_TIME_SEC&signature=SIGNATURE  

Could you please post example of successful POST request ?

1 person has this problem


You're probably better off asking the devs here:

randomString = "";

  byte[] key = Encoding.UTF8.GetBytes("scrt_code");



            byte[] message = Encoding.UTF8.GetBytes(randomString);

            var hash = new HMACSHA256(key);

            byte[] hashb = hash.ComputeHash(message);

            return BitConverter.ToString(hashb).Replace("-", "").ToLower();

I'm using C#, this way the hash not returning properly... can u someone advice?

Well that was a waste of dev time - thank you Jay and Tom for sharing the solution.

Including the parameters in the body also solved this for me - however it's unexplained and not documented in the docs

Thank you Jay. I’ve tested this solution and can confirm that passing parameters in the POST body rather than in a query string indeed helps to avoid receiving “unauthorized” status...

1 person likes this

Andrew: make sure to add all parameters (form encoded) to the request body of the POST request, and not only as query string parameters.

The problem with POST requests returning "Unauthorized" status start happening again in environment...

Could you please validate if POST request working correctly in stagingost? No problems with GET requests...

Just for people visiting -  solution:

signature is derived from:


POST request :



Hello Tom. You can find us on for technical questions / chat.

I used Python but same result and I also tried every possible combination. I also used curl with same result. Always 401.

I am having the same issue. I can perform GET requests fine, however, POST requests are a no-go.

I have tried constructing  the request a variety of ways, but it always seems to yield a 401. Are you using the Ruby SDK? Does anyone know if it works within that?

1 person likes this
Login to post a comment