Facing issue with the Bitfinex API Key ans Secret Key.

[bitfinexcom]

Facing issue with the Bitfinex API Key ans Secret Key.

[mangukiya-ketan]

Yes, I am also getting the same errors, even i tried by different different API Key and Secret Pair, but in Each POST API i am getting "Bitfinex::BadRequestError: Nonce is too small."
Please let us know, if there is some fault from our side in calling those API or anything.
Thank you

[prdn]

Can you try creating a new API key?

…

On Fri, 5 Oct 2018 at 14:35, Ketan Mangukiya ***@***.***> wrote: Yes, I am also getting the same errors, even i tried by different different API Key and Secret Pair, but in Each API i am getting "Bitfinex::BadRequestError: Nonce is too small." — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#73 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADks7dJqvX5jDFSnjotd0aBhkHO-ViyJks5uh1IhgaJpZM4XKAVT> .

-- -- Paolo Ardoino

[mangukiya-ketan]

Thank you for response, as you told us i tried with new API Key-Secret but still i am getting the same again.

[face]

Hi, I'm looking into your issue.

I am unable to reproduce this issue on my end. What I tried is generating a new API key, and then used this gem to place orders and check balances.

The Nonce is simply an increasing sequence number. This gem is calculating the Nonce using time.

Some possible causes to the above error:

1. Using the API keys with different clients might be calculating the Nonce differently (for example, this gem, a Node client, the mobile client, a custom API script might use nanoseconds vs microseconds). Are you using the API keys with any other scripts or clients before the above test?
2. Using the API key on multiple computers with the clocks time differing could also cause a Nonce error.

Each API key has its own Nonce. So as long as all clients using that key are calculating the Nonce the same way and it is always increasing, you should not see the above error. If you are generating a fresh key and only using in the example you provided, we will need to investigate this further.

[ramror3]

Hi,
I fixed this issue. I defined one method for the nonce. Its working fine now.
Thanks.