Rust module to connect to okx v5 websocket
Budget: $750 – $1,500 SGD
Rust module developer needed to create a module that connects to okx api v5 via WebSocket.
Expected timeline: less than 1 week to completion.
Module requirements:
- create a rust module similar to the binance-rs crate, but for okx v5 instead
- like binance-rs, it should use the tungstenite crate to manage the websocket connection, and be similarly threadsafe
- it should be able to connect to the okx v5 websocket api detailed here: https://www.okx.com/docs-v5/en/#websocket-api
- it should be able to connect to the public ws api endpoint, and it should allow subscription to the following channels (including enums and definitions for return objects): Trades channel & Orderbook channel
- it should be able to connect to the private ws api endpoint, based on api credentials passed into the module, and it should allow subscription to the following channel (including enums and definitions for return objects): Order Channel
- the module connected to the private ws endpoint should also be able to request (and pass back response) of the following ws request/response calls: (trade) Place order, Cancel order & Amend order.
- It should accept a string which specifies the websocket endpoint to connect to.
Finally there should be an example file of how to use the module for all above functionality. Code quality is important, as well as keeping an eye on latency and overheard.
Expected timeline: less than 1 week to completion.
Module requirements:
- create a rust module similar to the binance-rs crate, but for okx v5 instead
- like binance-rs, it should use the tungstenite crate to manage the websocket connection, and be similarly threadsafe
- it should be able to connect to the okx v5 websocket api detailed here: https://www.okx.com/docs-v5/en/#websocket-api
- it should be able to connect to the public ws api endpoint, and it should allow subscription to the following channels (including enums and definitions for return objects): Trades channel & Orderbook channel
- it should be able to connect to the private ws api endpoint, based on api credentials passed into the module, and it should allow subscription to the following channel (including enums and definitions for return objects): Order Channel
- the module connected to the private ws endpoint should also be able to request (and pass back response) of the following ws request/response calls: (trade) Place order, Cancel order & Amend order.
- It should accept a string which specifies the websocket endpoint to connect to.
Finally there should be an example file of how to use the module for all above functionality. Code quality is important, as well as keeping an eye on latency and overheard.