Deribit API
max_show query parameter removal on /api/v2/private/buy
Deprecated, no dateSubscribe to Deribit APIShare
Deribit API deprecated /api/v2/private/buy, query parameter max_show without giving a shutdown date yet.
Calls it hits
/api/v2/private/buyquery parameter max_show
What to use instead of these calls
Send display_amount instead of max_show.
In Deribit API's words
Deprecated the max_show parameter and introduced display_amount to define the visible portion of an iceberg order.
Facts
- API
- Deribit API
www.deribit.com - Kind
- Parameter removal
- Announced
- June 10, 2025
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Deribit API's own pages
Questions
When does this change take effect?
Deribit API deprecated /api/v2/private/buy, query parameter max_show without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Deribit 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 Deribit API 10
-
/api/v2/private/buyParameter removal Stopped working -
/api/v2/private/edit*Parameter removal Stopped working -
/api/v2/private/sellParameter removal Stopped working -
/api/v2/private/toggle_portfolio_marginingEndpoint removal Stopped working -
/api/v2/private/get_portfolio_marginsEndpoint removal Stopped working -
/api/v2/public/get_portfolio_marginsEndpoint removal Stopped working -
/api/v2/public/get_indexEndpoint removal Stopped working -
No date
/api/v2/private/get_pending_block_tradesEndpoint removal Deprecated, no date -
No date
/api/v2/private/editParameter removal Deprecated, no date -
No date
/api/v2/private/sellParameter 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.