---
title: "Strike-level flow concentration"
method: GET
path: "/v1/flow/{ticker}/strikes"
tags: ["Flow"]
---

# Strike-level flow concentration

`GET /v1/flow/{ticker}/strikes`

Where the directional money is going for `{ticker}`. Top-N strikes
by selected ordering (premium, net premium, volume, etc.) with
bullish/bearish premium split, ask/bid mix, and OI context. Includes
a top-3 concentration summary.

## Path parameters

- `ticker` string, required

## Query parameters

- `start_time` string, required
- `end_time` string, required
- `top_n` integer
- `right` 'call' | 'put'
- `min_premium` number, double
- `order_by` 'net_premium' | 'total_premium' | 'volume'
- `min_dte` integer
- `max_dte` integer

## Response `200`

Top-N strike rollup.

- StrikesSuccess
  - `data` StrikesResponse, required
    - `ticker` string, required
    - `startTime` string, date-time, required
    - `endTime` string, date-time, required
    - `byStrike` StrikeBreakdown[], required
      - `strike` number, required
      - `right` 'C' | 'P', required
      - `dominantExpiration` string, date, required
      - `tradeCount` integer, required
      - `volume` integer, required
      - `totalPremium` number, required
      - `bullishPremium` number, required
      - `bearishPremium` number, required
      - `netPremium` number, required
      - `askPct` number, required — Share of premium executed at-or-above ask (aggressive buying).
      - `bidPct` number, required — Share of premium executed at-or-below bid (aggressive selling).
      - `openInterest` integer, required
      - `volOiRatio` number, required
    - `concentration` StrikesConcentration, required
      - `top3StrikesShare` number, required — Share (0–1) of the window's premium concentrated in the top 3 strikes.
      - `top3StrikesNetPremium` number, required
      - `interpretation` string, required
  - `meta` Meta, required
    - `timestamp` string, date-time, required — Server-side timestamp the response was generated at.
    - `requestId` string, required — Short opaque ID for log correlation.

## Other responses

- `400` — Request validation failed.
- `401` — Missing or invalid API key.
- `402` — The account's shared Skylit credit balance is lower than this route's cost. Top up to continue. Carries `X-Credits-Remaining: 0`.
- `403` — API key revoked/expired, monthly quota exceeded, or the account's API access is suspended (`account_suspended`).
- `429` — Per-minute rate limit exceeded.
- `503` — Underlying data source temporarily unavailable, or the credit balance could not be verified (`credit_check_failed`). Safe to retry.

---

[API](https://skmtc.net/skylit/apis/flowseeker-skylit-public-api.md) · [All operations](https://skmtc.net/skylit/apis/flowseeker-skylit-public-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/skylit/flowseeker-skylit-public-api/revisions/3280190b1b24/schema)