Skip to content

Migrate to Bitget API V2#5

Closed
gering wants to merge 1 commit intomainfrom
feature/migrate-to-api-v2
Closed

Migrate to Bitget API V2#5
gering wants to merge 1 commit intomainfrom
feature/migrate-to-api-v2

Conversation

@gering
Copy link
Copy Markdown
Owner

@gering gering commented Feb 1, 2026

Summary

  • Bitget deprecated API V1, causing "Bad Request" errors
  • Migrated all endpoints to API V2 format
  • Updated productTypes from umcbl/dmcbl/cmcbl to USDT-FUTURES/COIN-FUTURES/USDC-FUTURES
  • Adapted response parsing for V2 structure (data arrays, lastPr instead of close)
  • Updated API-SPEC.md documentation

Test plan

  • Tested spot account balance fetching
  • Verified cryptocurrency prices are retrieved correctly
  • Test futures positions (if available)

🤖 Generated with Claude Code

- Update all endpoints from V1 to V2 format
- Change productTypes: umcbl -> USDT-FUTURES, etc.
- Adapt response parsing for V2 structure (data arrays, lastPr field)
- Use 'coin' field instead of 'coinName' for spot assets
- Remove MoneyMoney signature for unsigned distribution
- Update API-SPEC.md documentation

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@gering gering force-pushed the feature/migrate-to-api-v2 branch from 124916a to c777d44 Compare February 1, 2026 11:43
@gering gering mentioned this pull request Feb 1, 2026
3 tasks
@gering
Copy link
Copy Markdown
Owner Author

gering commented Feb 1, 2026

Superseded by #6 which includes changes from #4 plus version bump.

@gering gering closed this Feb 1, 2026
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.

1 participant