Question Regarding `/user/spot/cancel_orders` and `/user/spot/orders_info`

[Harui-i]

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.

[soichirokodama]

Thank you for pointing this out.

There are some parts in Docs that are not formatted properly, so we plan to review the whole thing and make corrections.

[koiibb]

Thank you for pointing out the inconsistency in the documentation.

To address this issue, we’ve updated the documentation by adding clarification regarding the shared content in the response, and we’ve also included the necessary response details in the form of tables for better consistency and clarity.

https://github.com/bitbankinc/bitbank-api-docs/blob/master/rest-api.md#cancel-order
https://github.com/bitbankinc/bitbank-api-docs/blob/master/rest-api.md#fetch-multiple-orders

If you have any further suggestions or questions, please don’t hesitate to let us know. Thank you again!