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
the drawbacks here is that the conversion from postman to openapi is lossy as the type info as well as which parameters are optional are lost. Instead everything becomes string, but at least the field names and paths are preserved as well as the comments
The text was updated successfully, but these errors were encountered:
Hello, the Futures (dapi or fapi) APIs are not part of this repository. They may become available in the long run, but there are limitations and different priorities at the moment, so it's not in the plan right now.
This being said, I'll close this issue, but with a "enhancement" tag. Thank you.
question
is this being slated as TODO on your side?
alternatively, is it available anywhere else?
side note
as a side note, this can be partially already done from the Postman definitions in the other repo using this pipeline:
For example for /dapi:
curl https://raw.githubusercontent.com/binance/binance-api-postman/master/collections/Binance%20Coin-M%20Futures%20API.postman_collection.json | postman2openapi | openapi-typescript
the drawbacks here is that the conversion from postman to openapi is lossy as the type info as well as which parameters are optional are lost. Instead everything becomes
string
, but at least the field names and paths are preserved as well as the commentsThe text was updated successfully, but these errors were encountered: