GET /api/v2/trading-pairs-info → endpoint removal
Bitstamp API
Deprecated, no date
The provider deprecated the GET /api/v2/trading-pairs-info endpoint without a shutdown date, noting that it is obsolete. Requests sent to this endpoint will eventually fail. The change was announced on October 15, 2024.
Calls it hits
GET /api/v2/trading-pairs-info
What to use instead of these calls
Call GET /api/v2/markets/ instead to retrieve the list of markets and their properties.
In Bitstamp API's words
GET /api/v2/trading-pairs-info/ is obsolete and replaced by endpoint api/v2/markets/
Facts
- API
- Bitstamp API
www.bitstamp.net - Kind
- Endpoint removal
- Announced
- October 15, 2024
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Bitstamp API's own pages
Questions
When does this change take effect?
Bitstamp API deprecated GET /api/v2/trading-pairs-info without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Bitstamp API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.