Skip to content

feat(v1.6.7): withdrawal id filters, 5xx retry docs, README ticker snippet - #150

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

tiagosiebler merged 2 commits into
sieblyio:masterfrom
JJ-Cro:update26102026

Conversation

@JJ-Cro

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

Copy link
Copy Markdown
Contributor

Summary

Adds withdrawal id filters, documents safe retries after 5xx on withdrawals and transfers, and adds a quick spot.tickers WebSocket snippet to the README.

Changelog

  • getWithdrawalRecords accepts withdraw_id and withdraw_order_id (GET /wallet/withdrawals); withdraw_id returns one record and disables the time filter
  • JSDoc on submitWithdrawal and submitMainSubTransfer: on HTTP 5xx or SERVER_ERROR the request may still have been accepted, so check getWithdrawalRecords({ withdraw_order_id }) or getTransferStatus({ client_order_id }) before resending
  • README: 3-line spot.tickers WebsocketClient snippet at the top (reconnect, heartbeat and resubscribe handled by the SDK)
  • regenerate endpoint docs and llms.txt
  • version 1.6.6 -> 1.6.7

Checks

  • lint, type tests, build pass
  • wsStore (9) and public (2) tests pass

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>

@tiagosiebler tiagosiebler left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@tiagosiebler
tiagosiebler merged commit ca08d21 into sieblyio:master Nov 2, 2026
1 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.

3 participants