At Get Force Liquidation Record (USER_DATA) (https://binance-docs.github.io/apidocs/spot/en/#get-force-liquidation-record-user_data - Discourse doesn’t let me “link to that host”), the documentation lists a “Mandatory - YES” timestamp parameter. That field is not actually mandatory, I could send requests without it. Either way, it would help to add an explanation for the timestamp field if it’s actually used.
Another error: liquidations are actually returned in ascending chronological order by the updatedTime field, but the documentation says “Response in descending order”.
the documentation lists a “Mandatory - YES” timestamp parameter. That field is not actually mandatory, I could send requests without it.
We were unable to reproduce a successful response omitting the timestamp field. Could you please share the full url used (omit any sensitive data) so that we can further diagnose?
Either way, it would help to add an explanation for the timestamp field if it’s actually used.
The timestamp field is explained in the documentation.
Timing security
A SIGNED endpoint also requires a parameter, timestamp, to be sent which should be the millisecond timestamp of when the request was created and sent.
An additional parameter, recvWindow, may be sent to specify the number of milliseconds after timestamp the request is valid for. If recvWindow is not sent, it defaults to 5000.