In the REST API documentation, many endpoints follow a structure where a table format of the response is shown after Response:, and an example in JSON format is provided after Response format: (for example, /user/assets/ here).
However, for /user/spot/cancel_orders (here) and /user/spot/orders_info (here), while there is an example in JSON format, there doesn’t appear to be a table format documentation. In the case of /user/spot/cancel_orders, there’s a JSON description following Response:, and for /user/spot/orders_info, there is a JSON format description after Response format:.
Is the absence of table format documentation for these endpoints because they share identical content with the tables for /user/spot/cancel_order and /user/spot/order, and thus are omitted for brevity?
I’ve confirmed this in both rest-api.md and rest-api_JP.md.
In the REST API documentation, many endpoints follow a structure where a table format of the response is shown after
Response:, and an example in JSON format is provided afterResponse format:(for example, /user/assets/ here).However, for
/user/spot/cancel_orders(here) and/user/spot/orders_info(here), while there is an example in JSON format, there doesn’t appear to be a table format documentation. In the case of/user/spot/cancel_orders, there’s a JSON description followingResponse:, and for/user/spot/orders_info, there is a JSON format description afterResponse format:.Is the absence of table format documentation for these endpoints because they share identical content with the tables for
/user/spot/cancel_orderand/user/spot/order, and thus are omitted for brevity?I’ve confirmed this in both rest-api.md and rest-api_JP.md.