You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You know I extended some Portofilio Margin Api in Binance.Net, and I found that some valid characters in client order id would be encoded in url, and then it would be rejected by regex checking of exchange.
For example, a colon ':' is valid in pm client order id regex ^[\.A-Z\:/a-z0-9_-]{1,32}$, but it would be encoded as %3A in request url if I use RestApiClient.SendToAddress. Then, exchange reject the order. I've contracted their tech support, and they told me not encode it.
However, it could be accepted in dapi and fapi, even if it was encoded.
So my question is:
May I have some options in RestApiClient , or I just avoid using these characters.
The text was updated successfully, but these errors were encountered:
You know I extended some Portofilio Margin Api in Binance.Net, and I found that some valid characters in client order id would be encoded in url, and then it would be rejected by regex checking of exchange.
For example, a colon ':' is valid in pm client order id regex
^[\.A-Z\:/a-z0-9_-]{1,32}$
, but it would be encoded as %3A in request url if I use RestApiClient.SendToAddress. Then, exchange reject the order. I've contracted their tech support, and they told me not encode it.However, it could be accepted in dapi and fapi, even if it was encoded.
So my question is:
May I have some options in RestApiClient , or I just avoid using these characters.
The text was updated successfully, but these errors were encountered: