> For the complete documentation index, see [llms.txt](https://docs.nexus.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexus.xyz/api-reference/markets/fetch-adl-events.md).

# GET /markets/{market\_id}/adl-events

Get ADL settlement history for a market (v0.21)

Get ADL settlement history for a market (v0.21).

`operationId`: `fetchAdlEvents`

> **Not reachable through CCXT.** ADL (auto-deleveraging) is a Nexus risk mechanism with no CCXT vocabulary.

**Authentication:** `hmacAuth`.

Returns up to `limit` ADL settlement events for the market, most recent first. Populated when the insurance fund is depleted and auto-deleveraging closes opposite-side positions to absorb bad debt.

## Parameters

| Name        | In    | Type      | Required | Default | Description                                                                                                                                                                                                                                                                                                                                                                                                                                            |
| ----------- | ----- | --------- | -------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `market_id` | path  | `string`  | Yes      | —       | Market identifier (e.g. BTC-USDX-PERP, ETH-USDX-PERP). Uppercase ASCII alphanumeric segments joined by single hyphens, at most 64 characters. A value outside that set is rejected with `400` (`INVALID_MARKET_ID`) before any store is read — it cannot name a market, so an empty result would assert that nothing traded rather than that the question was malformed. A well-formed identifier that names no listed market is a `404`, not a `400`. |
| `limit`     | query | `integer` | No       | `100`   | —                                                                                                                                                                                                                                                                                                                                                                                                                                                      |

## Responses

| Status | Body                                                                         | Meaning                                |
| ------ | ---------------------------------------------------------------------------- | -------------------------------------- |
| `200`  | array of [`AdlEventRecord`](/api-reference/guides/schemas.md#adleventrecord) | ADL settlement history for the market. |
| `400`  | — *(no schema declared)*                                                     | —                                      |
| `401`  | — *(no schema declared)*                                                     | —                                      |
| `429`  | — *(no schema declared)*                                                     | —                                      |

## Example

{% tabs %}
{% tab title="cURL" %}

```bash
curl -X GET 'https://exchange.nexus.xyz/api/exchange/markets/BTC-USDX-PERP/adl-events' \
  -H 'X-API-Key: nx_7f3a1b...' \
  -H 'X-Timestamp: 1776033911836' \
  -H 'X-Signature: <hmac-sha256>'
```

{% endtab %}

{% tab title="Python" %}

```python
import requests

headers = {
    "X-API-Key": "nx_7f3a1b...",
    "X-Timestamp": "1776033911836",
    "X-Signature": "<hmac-sha256>"
}

response = requests.get("https://exchange.nexus.xyz/api/exchange/markets/BTC-USDX-PERP/adl-events", headers=headers)
response.raise_for_status()
print(response.json())
```

{% endtab %}

{% tab title="TypeScript" %}

```typescript
const response = await fetch("https://exchange.nexus.xyz/api/exchange/markets/BTC-USDX-PERP/adl-events", {
  method: "GET",
  headers: {
    "X-API-Key": "nx_7f3a1b...",
    "X-Timestamp": "1776033911836",
    "X-Signature": "<hmac-sha256>"
  },
});
if (!response.ok) throw new Error(`${response.status} ${await response.text()}`);
console.log(await response.json());
```

{% endtab %}
{% endtabs %}

`X-Signature` is a placeholder: it is derived from this specific request. See [Authentication](/api-reference/guides/authentication.md) for the canonical string and the HMAC rule.

***

<sub>Generated from</sub> <sub></sub><sub>`eng/apps/exchange/api/openapi.json`</sub> <sub></sub><sub>(spec</sub> <sub></sub><sub>`0.9.73`</sub><sub>). Do not edit by hand — regenerate with</sub> <sub></sub><sub>`python3 product/docs/tools/api-reference/generate.py`</sub><sub>. Hand-authored context lives in the Guides pages.</sub>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nexus.xyz/api-reference/markets/fetch-adl-events.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.