GET /derivatives/api/v3/feeschedules/volumes → endpoint removal
Kraken Futures API
Deprecated, no date
The provider deprecated the GET /derivatives/api/v3/feeschedules/volumes endpoint on June 22, 2026, without a shutdown date. This change affects calls to that endpoint on futures.kraken.com. Once shut down, requests to the endpoint will fail.
Calls it hits
GET /derivatives/api/v3/feeschedules/volumes
What to use instead of these calls
Read the fee rate applied to Futures trades from the Spot POST /0/private/TradeVolume endpoint on api.kraken.com using a Spot API key.
In Kraken Futures API's words
DEPRECATED the Futures Fee Schedules endpoints and related fields
Facts
- API
- Kraken Futures API
futures.kraken.com - Kind
- Endpoint removal
- Announced
- June 22, 2026
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Kraken Futures API's own pages
Questions
When does this change take effect?
Kraken Futures API deprecated GET /derivatives/api/v3/feeschedules/volumes without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Kraken Futures 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.
More from Kraken Futures API 1
-
No date
GET /derivatives/api/v3/feeschedulesEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.