Error Binance API: "Timestamp for this request is outside of the recvWindow"
See original GitHub issueI’m trying to perform a GET request to the Binance’s API using Postman. I read all the post about the time sync (I’m using Windows and I tried “net stop w32time, w32tm /unregister, w32tm /register, net start w32time, w32tm /resync”), I tried another Windows machine, and I tried to set every value of timestamp or recWindow but I still cannot perform this request. Could you help me out? Thanks
GET request:
https://api.binance.com/api/v3/allOrders?timestamp=2326558065&signature=SECRETKEY&recvWindow=50000
And as a header X-MBX-APIKEY=APIKEY But i get:
{
"code": -1021,
"msg": "Timestamp for this request is outside of the recvWindow."
}
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Error "Timestamp for this request is outside of the recvWindow"
Reason: The request's timestamp is not synchronized enough with our server's time to receive response within the defined recvWindow.
Read more >Binance: Timestamp for this request is outside of the ... - GitHub
I have just 1 problem about binance api. When i put my binance key and binance secret i got this error. binance {"code":-1021,"msg":"Timestamp...
Read more >Binance TIMESTAMP ERROR (Timestamp for this request is ...
I got this error : data: { code: -1021,enter code here msg: 'Timestamp for this request is outside of the recvWindow.' } Then...
Read more >ccxt-dev/ccxt - Gitter
I updated ccxt but doesn't resolve this Error: binance {"code":-1021,"msg":"Timestamp for this request is outside of the recvWindow."}.
Read more >Errors with Binance connection - Quantower Help
Error "Timestamp for this request is outside of the recvWindow". The platform synchronizes time with the Binance exchange during the connection.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thank you very much for your answer. Ok I will check CCXT. Thank you again!
@lRninG9977
Tbh, I don’t really think about it, since I am not responsible for developing or maintaining that software.
In general, it is a well-known project, so it doesn’t steal your credentials. It is open-source and you can review the source code to see what exactly it is doing with your keys. CCXT does the same, otherwise nobody would trust it and nobody would use it. I would recommend you to use CCXT, of course.