Binance USDⓈ-M Futures API
GET /papi/v1/cm/income changes: page parameter no longer supported
Stopped workingSubscribe to Binance USDⓈ-M Futures APIShare
On October 28, 2026, the Binance USDⓈ-M Futures API changed the behavior of the GET /papi/v1/cm/income endpoint. The query parameter page is no longer supported on this endpoint. Calls that continue to send this parameter fail since that date.
Calls it hits
GET /papi/v1/cm/incomequery parameter page
What to use instead of these calls
Update requests to use startTime and endTime to locate records instead of the page parameter.
In Binance USDⓈ-M Futures API's words
- GET /papi/v1/cm/income (Get CM Income History): the page parameter is no longer supported. Use startTime and endTime to locate records.
Facts
- API
- Binance USDⓈ-M Futures API
fapi.binance.com - Kind
- Behaviour change
- Announced
- October 21, 2026
- Takes effect
- October 28, 2026
- Calls after that day
- Fail
- Source
- Changelog
- Last updated
- Verified
- , against Binance USDⓈ-M Futures API's own pages
Questions
When does this change take effect?
Calls to GET /papi/v1/cm/income, query parameter page on Binance USDⓈ-M Futures API stopped working on October 28, 2026.
What happens to calls after October 28, 2026?
They have failed since October 28, 2026.
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 Binance USDⓈ-M Futures API 9
-
GET /fapi/v1/accountEndpoint removal Stopped working -
GET /fapi/v1/balanceEndpoint removal Stopped working -
GET /fapi/v1/positionRiskEndpoint removal Stopped working -
GET /dapi/v1/incomeBehaviour change Stopped working -
GET /fapi/v1/incomeBehaviour change Stopped working -
GET /papi/v1/um/incomeBehaviour change Stopped working -
No date
GET /fapi/v2/accountEndpoint removal Deprecated, no date -
No date
GET /fapi/v2/balanceEndpoint removal Deprecated, no date -
No date
GET /fapi/v2/positionRiskEndpoint removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.