Skip to content

feat(v1.6.7): withdrawal record filters and spot ticker snippet - #6

Merged
JJ-Cro merged 2 commits into
masterfrom
update26102026
Nov 2, 2026
Merged

JJ-Cro merged 2 commits into
masterfrom
update26102026

Conversation

@JJ-Cro

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

Copy link
Copy Markdown
Owner

Summary

Gate withdrawal list filters and a short public ticker example at the top of the README. Version 1.6.7. Branched from upstream master 0db35ae after sieblyio#148 and sieblyio#149.

Changelog

  • getWithdrawalRecords accepts withdraw_id and withdraw_order_id on GET /wallet/withdrawals. withdraw_id returns that one record and disables the time filter. Deposit queries stay on the shared params type.
  • JSDoc on submitWithdrawal and submitMainSubTransfer: on HTTP 5xx or SERVER_ERROR, the call may still have been accepted. Check getWithdrawalRecords({ withdraw_order_id }) or getTransferStatus({ client_order_id }) before sending it again.
  • README: 3-line spot.tickers WebsocketClient snippet near the top. The SDK handles reconnect, heartbeat, and resubscribe.

Skipped: Crossex 4xx idempotency note, still waiting on a staff answer.

Checks

  • npx eslint src clean
  • npx tsc -p test/tsconfig.test.json --noEmit clean
  • npm run build clean
  • Tests: wsStore 9 passed, public.test.ts 2 passed
  • private.test.ts not run (needs API keys)
Open in Web Open in Cursor 

cursoragent and others added 2 commits October 26, 2026 08:09
1.6.7

- getWithdrawalRecords accepts withdraw_id and withdraw_order_id
- JSDoc on submitWithdrawal and submitMainSubTransfer: on HTTP 5xx or SERVER_ERROR, check withdrawal records or getTransferStatus(client_order_id) before resending
- README: 3-line spot.tickers snippet near the top (reconnect, heartbeat, resubscribe)

Skipped: Crossex 4xx idempotency note, still waiting on a staff answer.

Co-authored-by: Jerko J <JJ-Cro@users.noreply.github.com>
@JJ-Cro
JJ-Cro merged commit ca08d21 into master Nov 2, 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