Skip to content

feat(v3.2.7): UTA Cash+ and 22 Oct fields - #4

Merged
JJ-Cro merged 5 commits into
masterfrom
update26102026
Oct 28, 2026
Merged

JJ-Cro merged 5 commits into
masterfrom
update26102026

Conversation

@JJ-Cro

@JJ-Cro JJ-Cro commented Oct 26, 2026 •

Copy link
Copy Markdown
Owner

Summary

UTA V3 batch for 20 Oct and 22 Oct. Cash+ earn endpoints, two new GETs, and the field additions on place-order, oi-limit, account info, strategy orders, and current funding rate.

UTA WS place-order and batch-place now send the broker code as top-level apiCode.

Branched from upstream master (67dcb80). update19102026 (upstream PR sieblyio#176) is already merged.

Live current-fund-rate returns the base rate as baselnterestRate (lowercase L). baseInterestRate is also typed for the docs name.

Changelog

  • Add Cash+ subscribe, redeem, positions, and history-orders for master and sub-accounts
  • Add GET /api/v3/market/margin-loans-all (coin optional) and GET /api/v3/copy/futures/copy-max-transferable
  • place-order: bboLevel (limit only) and slippageTolerance (market only, default 0.02, range 0.01-0.05)
  • oi-limit: singlePositionRatio and totalPositionRatio
  • account/info: traderType
  • unfilled and history strategy orders: marginMode
  • current-fund-rate: lastFundingRate, nextFundingRate, baseInterestRate, impactMarginNotional
  • Live current-fund-rate spells the base rate baselnterestRate
  • JSDoc: market orders always run as IOC; futures qty must match quantityMultiplier and quantityPrecision; error 25159 is a 5x cap in a low-liquidity period, with no pre-check API
  • UTA WS place-order and batch-place send top-level apiCode, default hbnni, matching the REST X-CHANNEL-API-CODE header. A caller apiCode replaces the default and is not copied into args
  • Cash+ history recordType is declared on the response. The response file no longer imports it from the request types

Checks

  • npm run lint
  • npm run build (tsc ESM + CJS)
  • npm run test:public was run before the added tests were removed

Skipped

  • StrategyOrderV3 side / posSide: still unconfirmed by Bitget. Existing side from 3.2.6 is unchanged.
  • receiveWindow: still unconfirmed. No further change. The 3.2.6 fields stay as they are.
  • Classic V2 WS trade: this SDK has no V2 WS order API. WebsocketClientV2.sendWSAPIRequest is a no-op. No apiCode to add there.
Open in Web Open in Cursor 

cursoragent and others added 5 commits October 26, 2026 08:15
- Add Cash+ subscribe, redeem, positions, and history-orders for master and sub-accounts
- Add GET /api/v3/market/margin-loans-all (coin optional) and GET /api/v3/copy/futures/copy-max-transferable
- place-order: bboLevel (limit only) and slippageTolerance (market only, default 0.02, range 0.01-0.05)
- oi-limit: singlePositionRatio and totalPositionRatio
- account/info: traderType
- unfilled and history strategy orders: marginMode
- current-fund-rate: lastFundingRate, nextFundingRate, baseInterestRate, impactMarginNotional
- Live current-fund-rate spells the base rate baselnterestRate
- JSDoc: market orders always run as IOC; futures qty must match quantityMultiplier and quantityPrecision; error 25159 is a 5x cap in a low-liquidity period, with no pre-check API

Co-authored-by: Jerko J <JJ-Cro@users.noreply.github.com>
- UTA WS place-order and batch-place send top-level apiCode, default hbnni, matching the REST X-CHANNEL-API-CODE header
- A caller apiCode replaces the default and is not copied into args

Co-authored-by: Jerko J <JJ-Cro@users.noreply.github.com>
- Earn response types no longer import EarnCashPlusRecordTypeV3 from the request types

Co-authored-by: Jerko J <JJ-Cro@users.noreply.github.com>
- Remove the WS apiCode payload test and the new public cases for funding rate, margin-loans-all, and oi-limit

Co-authored-by: Jerko J <JJ-Cro@users.noreply.github.com>
@JJ-Cro
JJ-Cro merged commit 14acfaa into master Oct 28, 2026
0 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants