---
title: "GetChokepointHistory"
method: GET
path: "/api/supply-chain/v1/get-chokepoint-history"
tags: ["SupplyChainService"]
---

# GetChokepointHistory

`GET /api/supply-chain/v1/get-chokepoint-history`

## Request

- Base URL: `https://api.worldmonitor.app`
- URL: `https://api.worldmonitor.app/api/supply-chain/v1/get-chokepoint-history`
- Auth: one of:
  - API key in header `X-WorldMonitor-Key`
  - API key in header `X-Api-Key`

GetChokepointHistory returns transit-count history for a single chokepoint, loaded lazily on card expand. Keeps the status RPC compact (no 180-day history per chokepoint on every call).

## Query parameters

- `chokepointId` string, required
- `jmespath` string

## Response `200`

OK

- WorldmonitorSupplyChainV1GetChokepointHistoryResponse
  - `chokepointId` string
  - `history` WorldmonitorSupplyChainV1TransitDayCount[]
    - `date` string
    - `tanker` integer
    - `cargo` integer
    - `other` integer
    - `total` integer
    - `container` integer
    - `dryBulk` integer
    - `generalCargo` integer
    - `roro` integer
    - `capContainer` number, double
    - `capDryBulk` number, double
    - `capGeneralCargo` number, double
    - `capRoro` number, double
    - `capTanker` number, double
  - `fetchedAt` string, int64

## Other responses

- `400`: Validation error
- `401`: Missing or invalid API key.
- `403`: API access requires an active subscription (the API key's subscription is inactive or expired).
- `429`: Rate limit exceeded.
- `503`: Service unavailable. Billing-verification responses include code and X-Billing-Verification; other gateway infrastructure failures use the generic GatewayError shape.
- `default`: Gateway or handler error response.

---

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