Bài viết này hiện không hỗ trợ trong ngôn ngữ bạn chọn và đã được tự động chuyển sang tiếng Anh.
Bitget Announcement on API System Encrypting Plaintext
Base on security concern, we plan to encrypt the plaintext UIDs of below interfaces in below pattern:
UID:3559776388 ---> encrypted UID: 706e2bd179b59a5f295c
Mean while, API server would accept either plaintext or encrypted UID as request parameter, for example the original request parameter UID: 3559776388 changes to the encrypted UID: 706e2bd179b59a5f295c
Changes involves below interfaces:
Future CopyTrade:
/api/mix/v1/trace/cancelCopyTrader
Request parameter 'traderId' accepts encrypted plaintext UID and encrypted UID;
/api/mix/v1/trace/traderList
Request parameter 'traderId' accepts encrypted plaintext UID and encrypted UID； response field 'traderUid' will be encrypted;
/api/mix/v1/trace/queryTraceConfig
Request parameter 'traderId' accepts encrypted plaintext UID and encrypted UID;
/api/mix/v1/trace/followerSetBatchTraceConfig r
Request parameter 'traderId' accepts encrypted plaintext UID and encrypted UID;
Spot CopyTrade：
/api/spot/v1/trace/order/orderHistoryList
Request field 'traderUserId' will be encrypted;
/api/spot/v1/trace/config/getFollowerSettings
Request parameter 'traderUserId' accepts encrypted plaintext UID and encrypted UID;
/api/spot/v1/trace/user/myTraders
Response field 'traderUid' will be encrypted;
/api/spot/v1/trace/config/setFollowerConfig
Request parameter 'traderUserId' accepts encrypted plaintext UID and encrypted UID;
/api/spot/v1/trace/user/myFollowers
Response field 'followerUserId' will be encrypted;
/api/spot/v1/trace/user/removeTrader
Request parameter 'traderUserId' accepts encrypted plaintext UID and encrypted UID;
Feel free to contact Bitget OPENAPI team(Telegram https://t.me/bitgetOpenapi) if any queries.
Chia sẻ
