---
title: "Get Max Pain Current"
method: GET
path: "/api/max-pain/current"
tags: ["Max Pain"]
---

# Get Max Pain Current

`GET /api/max-pain/current`

## Request

- Base URL: `https://api.zerogex.io` (the document declares no server; this is the origin it was published from)
- URL: `https://api.zerogex.io/api/max-pain/current`
- Auth: HTTP bearer

Get current max pain and strike-by-strike call/put payout notional.

The top-level ``timestamp``, ``max_pain``, ``underlying_price``, and
``difference`` fields reflect the latest analytics-engine reading and
agree with the most recent point in ``/api/max-pain/timeseries``.

The ``expirations[]`` array (per-expiration max pain plus the full
call/put payoff curve at each settlement candidate) comes from a
daily pre-market snapshot — open interest only publishes once per
day at settlement, so this detail is stable through the trading day.

## Query parameters

- `symbol` string
- `strike_limit` integer

## Response `200`

Successful Response

- MaxPainCurrent
  - `timestamp` string, date-time, required
  - `symbol` string, required
  - `underlying_price` string, required
  - `max_pain` string, required
  - `difference` string, required
  - `expirations` MaxPainExpiration[], required
    - `expiration` string, date, required
    - `max_pain` string, required
    - `difference_from_underlying` string, required
    - `strikes` MaxPainPoint[], required
      - `expiration` string, date, nullable
      - `settlement_price` string, required
      - `call_notional` string, required
      - `put_notional` string, required
      - `total_notional` string, required

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/zerogex/apis/zerogex-api.md) · [All operations](https://skmtc.dev/zerogex/apis/zerogex-api/llms.txt) · [OpenAPI document](https://skmtc.dev/zerogex/apis/zerogex-api/revisions/753b26bf0592?raw)