binance / binance/binance-public-data
Liquidation Data Endpoint `/fapi/v1/forceOrders` and Historical Files Unavailable (Geo-blocked / Removed)
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 613
- PR merge metrics
- No merged PRs in 30d
Description
Hello Binance team,
I would like to report that access to the following endpoint appears to be "inaccessible due to geolocation restrictions".
From: GET https://fapi.binance.com/fapi/v1/forceOrders
Requests return HTTP 451:
{
"msg": "Service unavailable from a restricted location according to 'b. Eligibility' in https://www.binance.com/en/terms"
}
This behavior persists even when connecting via IPs located in previously unrestricted regions (e.g. Japan, Singapore), and makes the endpoint effectively unusable for all non-whitelisted IPs.
Additionally, the historical liquidation snapshot files formerly available under "https://data.binance.vision/data/futures/um/daily/liquidationSnapshot/"
have been entirely removed from both the data listing, server and binance api docs!
- Is the /fapi/v1/forceOrders endpoint being deprecated or permanently geo-blocked?
- Will historical liquidation data (ZIP/CSV files) be restored or made available via any alternative channel (e.g. authenticated API, data feed, or cloud archive)?
-Could Binance clarify its current policy or plans regarding public access to liquidation data for research, auditing, or transparency purposes?
This dataset has been crucial for building accurate market risk models and studying derivatives behavior.
A lack of access prevents reproducibility of research and inhibits trust.
Any update would be greatly appreciated.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by checking GET https://fapi.binance.com/fapi/v1/forceOrders and the historical liquidationSnapshot listing at https://data.binance.vision/data/futures/um/daily/liquidationSnapshot/. Compare the HTTP 451 response, the Binance API documentation, and the missing ZIP/CSV files; the issue is complete only when the access policy or a restored or alternative data source is clarified.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100