---
title: "Page counterparty executions"
method: GET
path: "/api/v1/whale-trades/{id}/counterparties/executions"
tags: ["Whale Trades"]
---

# Page counterparty executions

`GET /api/v1/whale-trades/{id}/counterparties/executions`

Returns a bounded execution page from the immutable snapshot emitted by whale-trade detail. A stale or changed snapshot returns a cursor-expired error so clients restart from detail.

## Path parameters

- `id` string, required

## Query parameters

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

## Response `200`

Counterparty execution page

- object
  - `object` 'counterparty_analysis', required
  - `data` CounterpartyAnalysis, required
    - `status` 'available' | 'partial' | 'unavailable', required
    - `unavailable_reason` string, nullable
    - `snapshot_id` string, nullable — Deterministic immutable membership snapshot for this detail response.
    - `analysis_id` string, nullable — Stable digest binding page cursors to one snapshot and execution set.
    - `execution_count` integer, required
    - `available_execution_count` integer, required
    - `unavailable_execution_count` integer, required
    - `executions` CounterpartyExecution[], required
      - `execution_id` string, required
      - `exchange_family` 'ctf_v2' | 'neg_risk_ctf_v2', required
      - `transaction_hash` string, required
      - `orders_matched_log_index` integer, required
      - `taker` CounterpartyParticipant, required
        - `counterparty_key` string, required
        - `execution_wallet` string, required — Lowercase Polygon wallet from the exact OrderFilled log.
        - `identity_status` 'resolved' | 'infrastructure' | 'unavailable', required
        - `resolved_user_id` string, nullable
        - `wallet_family` string, nullable
        - `resolution_block` integer, nullable
        - `resolution_source` string, nullable
        - `display_name` string, nullable
        - `grade` string, nullable
        - `maker_fill_count` integer, required
        - `filled_shares` string, required — Exact decimal shares.
        - `filled_usdc` string, required — Exact decimal USDC amount.
        - `share_pct` string, required — Participant share of the exact execution, from 0 through 100.
        - `match_breakdown` CounterpartyMatchBreakdown[], required
          - `match_type` 'COMPLEMENTARY' | 'MINT' | 'MERGE', required
          - `maker_fill_count` integer, required
          - `filled_shares` string, required — Exact decimal shares.
      - `makers` CounterpartyParticipant[], required
        - `counterparty_key` string, required
        - `execution_wallet` string, required — Lowercase Polygon wallet from the exact OrderFilled log.
        - `identity_status` 'resolved' | 'infrastructure' | 'unavailable', required
        - `resolved_user_id` string, nullable
        - `wallet_family` string, nullable
        - `resolution_block` integer, nullable
        - `resolution_source` string, nullable
        - `display_name` string, nullable
        - `grade` string, nullable
        - `maker_fill_count` integer, required
        - `filled_shares` string, required — Exact decimal shares.
        - `filled_usdc` string, required — Exact decimal USDC amount.
        - `share_pct` string, required — Participant share of the exact execution, from 0 through 100.
        - `match_breakdown` CounterpartyMatchBreakdown[], required
          - `match_type` 'COMPLEMENTARY' | 'MINT' | 'MERGE', required
          - `maker_fill_count` integer, required
          - `filled_shares` string, required — Exact decimal shares.
      - `makers_next_cursor` string, nullable — Stable cursor after the last maker included in the bounded inline page.
    - `executions_next_cursor` string, nullable — Stable cursor after the last execution included in the bounded inline page.
  - `meta` ResponseMeta, required
    - `request_id` string, required — Unique request ID (req_ prefix).
    - `cached` boolean, required
    - `cache_age_s` integer, nullable — Cache age in seconds. Omitted when the response was not cached, and also when it was cached but its age cannot be established (an entry stored before its cache carried a computed instant). Never a placeholder: an unknown age is reported as no value rather than as the cache TTL.
    - `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 list 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

- `400` — Bad request. On this cursor-paginated route a 400 has TWO distinct causes; branch on error.reason. (1) error.reason="cursor_expired" (with error.param="cursor"): the pagination cursor was invalidated by an upstream data change mid-walk (e.g. the ranking snapshot behind the page refreshed). It is NOT a malformed parameter and NOT a reason to stop: recovery is mechanical -- re-request the first page and walk forward again. There is deliberately no Retry-After and no error.retry_at, because waiting changes nothing. (2) no error.reason: an ordinary invalid request parameter -- check error.param when present, otherwise error.message. Both carry error.code="bad_request" (a FROZEN contract value), so error.reason is the discriminator.
- `401` — Missing or invalid API key
- `402` — Active Pro subscription required
- `403` — Account access denied
- `404` — Resource not found
- `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.
- `503` — Service unavailable. On this route a 503 has TWO distinct causes; branch on error.reason. (1) error.reason="read_model_warming": the requested endpoint cannot serve its read model yet. Exact causes are endpoint-specific and can include a cold or contended refresh or a dependency that prevented refresh; consult that endpoint's contract and do not infer dependency health from this shared reason. This is endpoint-local unavailability, not rate limiting: retry only this route after Retry-After (or error.retry_at), and do not feed it into a rate-limit backoff shared with other endpoints. (2) no error.reason: the Redis-backed authenticated rate limiter is unavailable and the middleware failed closed; Retry-After is the seconds until it probes Redis again. Both carry error.code="rate_limit_unavailable" (a FROZEN contract value, so it cannot be split per cause) and X-Request-Id -- which is why error.reason, not error.code, is the discriminator.

---

[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/revisions/be0e25f93c7d/schema)