> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

# liquidatable | Hyperliquid info

> The info endpoint with type: "liquidatable" checks whether a user's positions are currently at risk of liquidation on the Hyperliquid exchange.

<Info>
  This method is available on Chainstack. Not all Hyperliquid methods are available on Chainstack, as the open-source node implementation does not support them yet — see [Hyperliquid methods](/docs/hyperliquid-methods) for the full availability breakdown.
</Info>

The `info` endpoint with `type: "liquidatable"` checks whether a user's positions are currently at risk of liquidation on the Hyperliquid exchange. This endpoint provides critical risk management information including liquidation status, leverage ratios, margin usage, and account health metrics.

## Parameters

### Request body

* `type` (string, required) — The request type. Must be `"liquidatable"` to check user's liquidation status.
* `user` (string, required) — Address in 42-character hexadecimal format (e.g., `0x31ca8395cf837de08b24da3f660e77761dfb974b`).

## Response

The response is an object containing liquidation status and risk metrics:

### Liquidation status fields

* `liquidatable` (boolean) — Whether the user's positions are currently liquidatable:
  * `true` — Positions are at risk and may be liquidated
  * `false` — Positions are healthy and not at liquidation risk

### Risk metrics (optional fields)

* `leverage` (string) — Current effective leverage ratio of the user's positions
* `marginUsed` (string) — Amount of margin currently used for open positions
* `marginRemaining` (string) — Amount of available margin before liquidation threshold
* `accountValue` (string) — Total account value including unrealized profit and loss
* `totalRawUsd` (string) — Total raw USD value of the account before adjustments
* `totalNtlPos` (string) — Total notional position value across all assets

### Understanding liquidation risk

**Liquidation occurs when:**

* Account leverage exceeds maximum allowed ratios
* Margin requirements are not met due to adverse price movements
* Account value falls below maintenance margin requirements

**Risk levels:**

* **Safe**: `liquidatable: false` with sufficient margin remaining
* **At Risk**: `liquidatable: true` indicating immediate liquidation danger
* **Critical**: High leverage with minimal margin remaining

## Example request

<CodeGroup>
  ```shell Shell theme={"system"}
  curl -X POST \
    -H "Content-Type: application/json" \
    -d '{"type": "liquidatable", "user": "0x31ca8395cf837de08b24da3f660e77761dfb974b"}' \
    https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/info
  ```

  ```python Python (hyperliquid-python-sdk) theme={"system"}
  from hyperliquid.info import Info

  # The Python SDK has no dedicated liquidatable() helper, so post the
  # request directly. Info.post() is the same primitive every typed
  # method wraps.
  info = Info("YOUR_CHAINSTACK_ENDPOINT", skip_ws=True)

  result = info.post(
      "/info",
      {"type": "liquidatable", "user": "0x31ca8395cf837de08b24da3f660e77761dfb974b"},
  )
  print(result)
  ```

  ```typescript TypeScript (@nktkas/hyperliquid) theme={"system"}
  import { HttpTransport, InfoClient } from "@nktkas/hyperliquid";

  const transport = new HttpTransport({ apiUrl: "YOUR_CHAINSTACK_ENDPOINT" });
  const info = new InfoClient({ transport });

  const result = await info.liquidatable();
  console.log(result);
  ```
</CodeGroup>

<Note>
  **Use your own endpoint in your code.** The code examples use a placeholder Chainstack endpoint (YOUR\_CHAINSTACK\_ENDPOINT) — replace it with your own Hyperliquid node endpoint from the [Chainstack console](https://console.chainstack.com/). The curl above uses a shared public endpoint for quick checks only; do not use it in production.
</Note>

## Use case

The `info` endpoint with `type: "liquidatable"` is essential for trading applications that need to:

* **Risk monitoring**: Continuously monitor account health and liquidation risk
* **Alert systems**: Trigger warnings when positions approach liquidation thresholds
* **Position management**: Make informed decisions about position sizing and leverage
* **Automated trading**: Implement risk management rules in trading bots
* **Portfolio dashboards**: Display real-time risk metrics and account health
* **Margin management**: Calculate available margin for new positions
* **Liquidation protection**: Automatically reduce positions when risk is high
* **Risk analytics**: Track leverage ratios and margin utilization over time
* **Trading interfaces**: Show visual indicators for account risk levels
* **Compliance monitoring**: Ensure positions stay within risk parameters
* **Emergency protocols**: Trigger emergency position closures when necessary
* **Performance analysis**: Understand the relationship between leverage and returns

This endpoint is critical for any serious trading application, as it provides the real-time risk assessment needed to prevent liquidations and manage portfolio risk effectively on the Hyperliquid exchange.


## OpenAPI

````yaml openapi/hyperliquid_node_api/hypercore_info/info_liquidatable.json post /4f8d8f4040bdacd1577bff8058438274/info
openapi: 3.0.0
info:
  title: Hyperliquid Node API
  version: 1.0.0
  description: This is an API for interacting with Chainstack Hyperliquid node.
servers:
  - url: https://hyperliquid-mainnet.core.chainstack.com
security: []
paths:
  /4f8d8f4040bdacd1577bff8058438274/info:
    post:
      tags:
        - hyperliquid operations
      summary: info (liquidatable)
      operationId: infoLiquidatable
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                type:
                  type: string
                  default: liquidatable
                  enum:
                    - liquidatable
                  description: Request type to check if user positions are liquidatable
                user:
                  type: string
                  default: '0x31ca8395cf837de08b24da3f660e77761dfb974b'
                  description: Address in 42-character hexadecimal format
              required:
                - type
                - user
      responses:
        '200':
          description: Liquidation status information for the user
          content:
            application/json:
              schema:
                type: object
                description: Information about user's liquidation status and risk metrics
                properties:
                  liquidatable:
                    type: boolean
                    description: Whether the user's positions are currently liquidatable
                  leverage:
                    type: string
                    description: Current leverage ratio of the user's positions
                  marginUsed:
                    type: string
                    description: Amount of margin currently used
                  marginRemaining:
                    type: string
                    description: Amount of margin remaining before liquidation
                  accountValue:
                    type: string
                    description: Total account value including unrealized PnL
                  totalRawUsd:
                    type: string
                    description: Total raw USD value of the account
                  totalNtlPos:
                    type: string
                    description: Total notional position value
                required:
                  - liquidatable

````