---
title: "Get a trader's position timeline for one market"
method: GET
path: "/api/v1/trader/{address}/position-timeline"
tags: ["Traders"]
---

# Get a trader's position timeline for one market

`GET /api/v1/trader/{address}/position-timeline`

Returns stored Polymarket fills for one tracked trader in one market, newest first, with server-computed running_amount and running_avg_price. The {address} segment accepts the same four identity shapes as the plural alias: 0x... wallet, username, trd_-prefixed trader id, or bare integer traders.id, resolved with precedence wallet -> trd_ -> integer -> username. Only HOT and WARM tier traders are tracked; other traders return 404. running_avg_price is a buy-weighted entry basis (sells do not change the running average) matching Polymarket /positions avgPrice semantics. Cursor-paginated.

## Path parameters

- `address` string, required

## Query parameters

- `condition_id` string, required
- `limit` integer
- `cursor` string

## Headers

- `If-None-Match` string

## Response `200`

Position timeline page

- object
  - `object` 'list', required
  - `data` PositionTimelineEvent[], required
    - `id` string, required — Prefixed ID (pe_...).
    - `event_timestamp` string, date-time, required — ISO 8601 timestamp of the on-chain fill.
    - `action` 'buy' | 'sell', required — From the taker's perspective.
    - `outcome_side` 'yes' | 'no', required
    - `token_id` string, nullable — The Polymarket CLOB token id (ERC1155 asset id, decimal string) for this outcome; null when unavailable (e.g. Kalshi markets, unsynced markets).
    - `amount_delta` number, required — Signed share delta (+ on buy, − on sell).
    - `price` number, required — Fill price in USDC per share, in [0,1].
    - `usdc_notional` number, required — Positive USDC notional of the fill.
    - `tx_hash` string, required — Polygon transaction hash of the fill.
    - `running_amount` number, required — Cumulative signed share balance after this fill.
    - `running_avg_price` number, required — Buy-weighted entry basis (matches Polymarket /positions avgPrice semantics). Sells do not change this value. 0 when no buys have occurred yet.
  - `has_more` boolean, required
  - `next_cursor` string, nullable
  - `total` integer, nullable — Total matching rows when the read model exposes a count; absent (or null) when it does not.
  - `meta` ResponseMeta, required
    - `request_id` string, required — Unique request ID (req_ prefix).
    - `cached` boolean, required
    - `cache_age_s` integer, nullable — Cache age in seconds, null if not cached.
    - `cost` integer, required — Advisory request weight (relative compute cost). 1 for simple reads; higher for heavier endpoints. Not a credit/price.
    - `directional_source` 'live' | 'degraded' — Which path produced the team-directional read on this response. Only present on endpoints that compute one (today: GET /api/v1/sports-edge-signals). "live" means the read RAN. "degraded" means it FAILED, so nothing was measured and the ranking fell back to raw conviction. The flag describes the READ, not its consequence: a read that ran and found nothing groupable also leaves the directional fields null, and that is honestly "live" -- the per-signal nulls already say "nothing to enrich here", so this snapshot-level flag carries only what they cannot, namely whether the read ran at all. A degraded response is cached on the shorter degraded TTL so it self-heals. Reported SEPARATELY from ranking_source because the two degradations are independent -- a smart-money DB miss weakens the ranking DATA, a directional failure removes a ranking WEIGHT -- and a consumer down-weighting a degraded response needs to know which input it lost. Omitted on endpoints that compute no directional read.
    - `ranking_source` 'live' | 'db_only' — Which ranking-data path produced this response. Only present on endpoints that can degrade a ranking (today: GET /api/v1/sports-edge-signals). "live" is the normal path (the current holder pile from the provider batch); "db_only" is the degraded fallback (a truthful but weaker trader_markets ranking) served when the live sharp-money ranking batch is unavailable (a smart-money DB read failure, not a Polymarket outage) and cached on a shorter TTL, so a consumer can down-weight or skip it. Omitted on endpoints that never degrade.
    - `category_skill_source` 'live' | 'partial' | 'degraded' | 'unavailable' — Whole filtered snapshot category-evidence status before pagination. Operational live always remains partial source coverage.
    - `category_skill_model_version` string
    - `category_skill_taxonomy_version` string
    - `category_skill_platform` 'polymarket'
    - `category_skill_scope` 'observed_goldsky_primary_taker_fill'
    - `category_skill_source_coverage` 'partial_whale_threshold_fills'
    - `category_skill_observation_started_at` string, date-time
    - `category_skill_model_operationally_degraded` boolean — Whole-model operational readiness captured with the category model snapshot. Present on category-enriched responses even when the filtered signal slate is empty. When true, category_skill_source is degraded and sports-edge-signals uses the shorter degraded cache TTL.
    - `category_skill_status_counts` object
      - `live` integer, required
      - `insufficient` integer, required
      - `stale` integer, required
      - `unknown` integer, required
      - `degraded` integer, required
    - `category_skill_base_payload_hash` string — SHA-256 of the funded signal membership/order/rank/cursor vector immediately before category-skill enrichment. Sports-edge-signals only.
    - `category_skill_enriched_base_payload_hash` string — Independent SHA-256 recomputation over the same base fields immediately after category-skill enrichment. Equality with category_skill_base_payload_hash proves shadow enrichment did not change funded inputs. Sports-edge-signals only.

## Other responses

- `304` — Not Modified. Returned when If-None-Match matches the current payload.
- `400` — Invalid request parameter
- `401` — Missing or invalid API key
- `402` — Active Pro subscription required
- `403` — Account access denied
- `404` — Not found. On this route a 404 has TWO distinct causes; branch on error.reason. (1) error.reason="trader_not_tracked": the wallet is real and the URL is right, but the trader sits outside the HOT/WARM sync tiers, so we capture no timeline for them. This is TERMINAL -- there is no Retry-After and no error.retry_at, because neither retrying nor re-spelling the path will ever succeed. Stop requesting this wallet. (2) no error.reason: the trader id or address does not resolve at all. Both carry error.code="not_found" (a FROZEN contract value), so error.reason is the discriminator -- and since this endpoint has singular and plural path spellings, "I used the wrong URL" is a plausible enough wrong guess that the distinction is worth branching on.
- `408` — Request exceeded the server's 30-second transport timeout. The timeout response has an empty body because it is generated before handler-level JSON error shaping.
- `423` — Account is locked
- `429` — Rate limit exceeded. Two independent budgets. (1) 100 requests/minute per user (sliding window), on every authenticated route. (2) On the BATCH routes only: 2500 batch item units/minute per user, reserved before any item is executed. A batch with N requested items costs N item units, including duplicate and invalid items. 2500 = 100 requests x 25 items per batch, which is the most item work a key can buy through the request limiter at all: a caller may spend their entire 100-request minute on full 25-item batches without the item budget being what stops them. The REQUEST budget is the effective ceiling, and batching is never the more expensive choice. The item budget can still deny at a sliding-window boundary (both counters carry the previous window forward with a floor, and the item counter runs 25x the request counter), so honor a 429 from either. Over-quota batches return 429 with Retry-After before any item work is done.
- `500` — Unexpected server error
- `503` — Redis-backed authenticated rate limiter unavailable; retry after the per-process outage cooldown

---

[API](https://skmtc.net/0xinsider/apis/0xinsider-api.md) · [All operations](https://skmtc.net/0xinsider/apis/0xinsider-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/0xinsider/0xinsider-api/versions/918e082b045a/schema)