GET /derivatives/api/v3/feeschedules → endpoint removal
Kraken Futures API
Deprecated, no date
Kraken deprecated the GET /derivatives/api/v3/feeschedules endpoint without a shutdown date. The provider announced on June 22, 2026, that it DEPRECATED the Futures Fee Schedules endpoints and related fields. Following this removal, calls to the endpoint will fail.
Calls it hits
GET /derivatives/api/v3/feeschedules
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 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/feeschedules/volumesEndpoint 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.