BitMEX API Update: GET /api/v1/user/csa now returns all active CSA loans
BitMEX is updating its API endpoint GET /api/v1/user/csa as part of ongoing product enhancements. Starting 11 June 2026, 06:00 UTC, the endpoint response format changes so traders and integrators can reliably read all active CSA loans tied to an account.
Previously, GET /api/v1/user/csa could return a single CSA object or a 204 No Content when no active loans existed. After the change, GET /api/v1/user/csa will always return 200 OK with a wrapper object containing an array: response.csas.
Empty response behavior also changes: if an account has no active CSAs, the API will return 200 OK with csas: [] instead of 204.
Accounts with multiple CSAs are now supported in the response. If more than one active CSA loan exists (typically one per collateral currency), all entries will be returned under csas.
The csaStatus field will reflect the full loan lifecycle. Cancelled and Rejected loans are excluded from the response. Possible statuses include New, PendingNew, MarginCall, Liquidated, Replaced, and PendingCancellation. All other fields (e.g., csaID, account, currency, amount, mmRatioMarginCall, maintMarginRatio) remain unchanged.
Action required: clients consuming GET /api/v1/user/csa should parse response.csas as an array, handle csas: [] with 200, and iterate over multiple entries when applicable.
Neutral
This is an API contract change, not a change to trading rules or risk parameters. For traders, the direct market impact should be limited. However, it can indirectly affect trading and monitoring systems that automate margin management, liquidation alerts, or exposure reporting—especially if they previously relied on 204 No Content or assumed a single CSA object.
In the short term, integrators may see errors or missing data if they don’t update their parsers, which could temporarily disrupt dashboards or automated strategies. In the longer term, the change improves data completeness and consistency by returning all active CSA loans and by standardizing the response to 200 OK with an array.
Compared with past exchange API revisions that require client-side parsing updates, the market reaction is typically neutral: liquidity and order books aren’t directly impacted, but operational frictions can occur for bots and analytics platforms.