First of all, thanks for the effort. In my journey to migrate my apps, I found some bugs (already reported) and took note of some general feedback that I’m posting below for your consideration:
-
list_orders
endpoint:limit
is marked as optional in the documentation, however, if you don’t set some value, you will get an error. - I’m wondering if the
create_order
andget_order
endpoints should return more similar response objects. - Sometimes, the errors don’t provide too much information, and it’s hard to know what was wrong with a bad request. See the example below:
text: '{"error":"INVALID_ARGUMENT","error_details":"order has been rejected","message":"order has been rejected"}'
- Different error response models between
accounts
andorders
endpoints. - Inconsistencies between
get_product
response andget_order/get_account
response. Forget_product
, the response object is adict
; however, forget_order
andget_account
, the response contains a field to access to the dict representing the account/order. -
get_product_candles
time format is expected as UNIX timestamps. For other endpoints, it needs to be in some specific ISO format (see list_orders as an example). Can we unify the format for date/time input? - There are differences between the example response and the documented response. See
get_trades
as examples. -
best_bid
andbest_ask
is not documented inget_trades
response.
I hope this can help improve the API endpoints.