ritmex-bot/docs/binance/binance-spot/websocket-api_request-format.md at 5aecaabb16f09aeac3e9b47c6e48845d5d2c173e

mzoe/ritmex-bot

Fork 0

mirror of https://github.com/discountry/ritmex-bot.git synced 2026-09-09 16:28:06 +00:00

Files

T

DisneyandGitHub d6399b92aa Feat/support binance (#22 )

* add docs

* Add Binance exchange support

- Updated the environment configuration to include Binance as a selectable exchange option.
- Enhanced the README documentation to reflect the addition of Binance.
- Implemented the Binance exchange adapter and integrated it into the existing exchange framework.
- Modified the basis arbitrage strategy to support Binance alongside existing exchanges.
- Added tests to ensure proper functionality and integration of Binance within the trading system.

* Enhance README with detailed Binance exchange configuration

- Added comprehensive instructions for setting up Binance as an exchange option.
- Included environment variable specifications for API keys, market types, and trading symbols.
- Provided examples for both perpetual and spot trading strategies.
- Clarified the use of WebSocket and REST for the Binance adapter.

* Enhance exchange support and testing framework

- Added a new test suite for exchange contracts to ensure consistency and functionality across supported exchanges.
- Refactored exchange ID handling to utilize a centralized list of supported exchanges, improving maintainability.
- Updated CLI argument parsing and help documentation to reflect the new exchange structure.
- Introduced utility functions for validating supported exchanges and their display names.
- Enhanced the BasisApp and strategy runner to leverage the new exchange validation logic.
- Added a new test command for running exchange-related tests.

* Refactor exchange contract tests and update CLI commands

- Removed the trailing supported exchanges set and simplified the logic for trailing stop support in the exchange contract tests.
- Updated the test command for exchange contracts to exclude unnecessary tests, streamlining the testing process.
- Enhanced test descriptions for clarity and improved understanding of the functionality being tested.

2026-02-27 11:37:44 +08:00

1.5 KiB

Raw Blame History

title, source, fetched_at

title	source	fetched_at
Request format \| Binance Open Platform	https://developers.binance.com/docs/binance-spot-api-docs/websocket-api/request-format	2026-02-26T10:38:13.107Z

Requests must be sent as JSON in text frames, one request per frame.

Example of request:

{    "id": "e2a85d9f-07a5-4f94-8d5f-789dc3deb097",    "method": "order.place",    "params": {        "symbol": "BTCUSDT",        "side": "BUY",        "type": "LIMIT",        "price": "0.1",        "quantity": "10",        "timeInForce": "GTC",        "timestamp": 1655716096498,        "apiKey": "T59MTDLWlpRW16JVeZ2Nju5A5C98WkMm8CSzWC4oqynUlTm1zXOxyauT8LmwXEv9",        "signature": "5942ad337e6779f2f4c62cd1c26dba71c91514400a24990a3e7f5edec9323f90"    }}

Request fields:

Name

Type

Mandatory

Description

id

INT / STRING / null

YES

Arbitrary ID used to match responses to requests

method

STRING

YES

Request method name

params

OBJECT

Request parameters. May be omitted if there are no parameters

Request id is truly arbitrary. You can use UUIDs, sequential IDs, current timestamp, etc. The server does not interpret id in any way, simply echoing it back in the response.

You can freely reuse IDs within a session. However, be careful to not send more than one request at a time with the same ID, since otherwise it might be impossible to tell the responses apart.
Request method names may be prefixed with explicit version: e.g., "v3/order.place".
The order of params is not significant.

1.5 KiB Raw Blame History

1.5 KiB

Raw Blame History