Kraken API
no_mpp body parameter removal on POST /0/private/EditOrder
Deprecated, no dateSubscribe to Kraken APIShare
The body parameter no_mpp on the POST /0/private/EditOrder endpoint has been deprecated. Kraken API deprecated it without a shutdown date. Calls that continue to pass this parameter will fail once removal takes effect.
Calls it hits
POST /0/private/EditOrderbody parameter no_mpp
What to use instead of these calls
Stop sending no_mpp in your requests.
In Kraken API's words
Deprecated no_mpp parameter on AddOrder, EditOrder, and AddOrderBatch
Facts
- API
- Kraken API
api.kraken.com - Kind
- Parameter removal
- Announced
- September 18, 2025
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Kraken API's own pages
Questions
When does this change take effect?
Kraken API deprecated POST /0/private/EditOrder, body parameter no_mpp without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Kraken 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 API 10
-
POST /0/public/*Endpoint removal Stopped working -
POST /0/private/StakeEndpoint removal Stopped working -
POST /0/private/Staking/*Endpoint removal Stopped working -
POST /0/private/UnstakeEndpoint removal Stopped working -
No date
POST /0/private/LedgersParameter removal Deprecated, no date -
No date
POST /0/private/AddOrderParameter removal Deprecated, no date -
No date
POST /0/private/AddOrderBatchParameter removal Deprecated, no date -
No date
POST /0/private/ClosedOrdersParameter removal Deprecated, no date -
No date
POST /0/private/LedgersParameter removal Deprecated, no date -
No date
POST /0/private/TradesHistoryParameter 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.