[vc_row][vc_column width=”1/4″][/vc_column][vc_column width=”1/2″][vc_single_image source=”featured_image” img_size=”large” add_caption=”yes” alignment=”center” style=”vc_box_rounded”][/vc_column][vc_column width=”1/4″][/vc_column][/vc_row][vc_row][vc_column width=”1/4″][/vc_column][vc_column width=”1/2″][vc_custom_heading text=”Binance API – Working with Signatures” font_container=”tag:h1|font_size:38|text_align:left|color:%230a0a0a” google_fonts=”font_family:Montserrat%3Aregular%2C700|font_style:700%20bold%20regular%3A700%3Anormal”][vc_separator color=”black” border_width=”3″][/vc_column][vc_column width=”1/4″][/vc_column][/vc_row][vc_row][vc_column width=”1/4″][/vc_column][vc_column width=”1/2″][vc_custom_heading text=”I’ll keep it short. Should you be using the Binance API and trying to retrieve data that needs a signed message, then you most likely will get the “Signature for this request is not valid“ error. I spent one day finding out what actually was the problem. No, it wasnt the recvWindow set to 5000. My timer was just 1 second off (1000ms). Here’s the solution. You only have to sign the ARGUMENT LIST, not the base url itself.. Just leave “https://api.binance.com/api/v3/order?“ out, sign the rest, put it all together and off you go.” font_container=”tag:div|font_size:16|text_align:justify|color:%230a0a0a” google_fonts=”font_family:Montserrat%3Aregular%2C700|font_style:400%20regular%3A400%3Anormal” css=”.vc_custom_1578601557998{margin-top: 10px !important;margin-right: 10px !important;margin-bottom: 10px !important;margin-left: 10px !important;}”][/vc_column][vc_column width=”1/4″][/vc_column][/vc_row][vc_row][vc_column width=”1/4″][/vc_column][vc_column width=”1/2″][/vc_column][vc_column width=”1/4″][/vc_column][/vc_row]
