> ## Documentation Index > Fetch the complete documentation index at: https://docs.0xinsider.com/llms.txt > Use this file to discover all available pages before exploring further. # Page maker counterparties > Returns a bounded maker-wallet page for one exact execution. Percentages keep the complete execution denominator across pages. Page the maker wallets on one exact execution of a whale trade. Use this endpoint when an execution carries a `makers_next_cursor`. ## Read the makers * `snapshot_id` is required. `execution_id` comes from the parent execution. * `items[]` carries `counterparty_key`, `execution_wallet`, `identity_status`, `display_name`, `grade`, `maker_fill_count`, `filled_shares`, `filled_usdc`, and `share_pct`. * `execution_wallet` is the lowercase Polygon wallet from the `OrderFilled` log. `identity_status` is `resolved`, `infrastructure`, or `unavailable`. * `share_pct` keeps the complete execution as its denominator on every page. * `match_breakdown[]` splits fills by `match_type`: `COMPLEMENTARY`, `MINT`, or `MERGE`. * `next_cursor` is bound to the analysis, the execution, the last share total, and the wallet. It is null on the last page. * `limit` is 1 to 100 with a default of 100. ## Handle the snapshot 1. Read `error.reason` on a `400`. `cursor_expired` means the snapshot expired or was invalidated. 2. Request the trade detail again. Restart from its new `snapshot_id`. 3. A `404` means the `snapshot_id` is unknown or belongs to another trade. 4. A `503` with `error.reason="read_model_warming"` means the counterparty runtime is unavailable. Retry this route after `Retry-After`. ```bash theme={null} curl -H "Authorization: Bearer $OXINSIDER_API_KEY" \ "https://api.0xinsider.com/api/v1/whale-trades/wt_123/counterparties/executions/$EXECUTION_ID/makers?snapshot_id=$SNAPSHOT_ID&limit=50" ``` ## Related [Page counterparty executions](/api-reference/endpoint/get-whale-trade-counterparty-executions) lists the executions that carry these makers. ## OpenAPI ````yaml GET /api/v1/whale-trades/{id}/counterparties/executions/{execution_id}/makers openapi: 3.1.0 info: x-generated-rate-limit-policy-from: web/src/lib/rate-limit-facts.ts via web/scripts/generate-api-policy.ts title: 0xinsider API description: >- Follow provider-exposed large-trade activity from Polymarket and Kalshi. Polymarket wallet-attributed trades can add grades, P&L, strategy, and diagnostic-score context when sufficient source data exists; Kalshi public prints remain anonymous, and fields can be null or unavailable. Normal API requests use a 30-second server timeout that returns HTTP 408 Request Timeout with an empty body when exceeded. Public REST /api/v1/* endpoints, excluding /api/v1/mcp, use Bearer-token based non-credentialed browser CORS: any Origin may call with Authorization, Content-Type, If-None-Match, Idempotency-Key, and Mcp-Session-Id request headers. Remote MCP at /api/v1/mcp is non-credentialed, but still validates Origin against the 0xinsider/localhost allowlist per MCP Streamable HTTP DNS-rebinding guidance. Successful browser CORS preflight responses advertise Access-Control-Max-Age: 86400. Browser JavaScript may read RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, the legacy X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, Retry-After, ETag, X-Request-Id, X-Request-Cost, X-Batch-RateLimit-Limit, X-Batch-RateLimit-Remaining, X-Batch-RateLimit-Reset, Mcp-Session-Id, and X-Mcp-Error-Code response headers. Credentialed first-party routes such as /api/keys, /api/billing, and auth endpoints remain restricted to configured 0xinsider origins. version: 1.0.0 contact: name: 0xinsider email: support@0xinsider.com url: https://0xinsider.com servers: - url: https://api.0xinsider.com description: >- Production (live data). Authenticate with a live key (oxi_sk_live_...); requires an active Pro subscription. security: - bearerAuth: [] tags: - name: Traders description: Trader intelligence, batch lookups, timelines, and export readiness. - name: Positions description: Current prediction-market position snapshots from backend-owned mirrors. - name: Large Positions description: Largest current open positions from graded traders (Polymarket-only). - name: Whale Trades description: Recent and historical large trade intelligence. - name: Leaderboard description: Ranked trader discovery and category/strategy leaderboards. - name: Pick of the Day description: >- One sourced sharp-money call a day: the side proven sharp money is backing, with pre-game odds, the proven holders, and the track record. - name: Markets description: Market search, discovery, snapshots, and smart-score flow. - name: Content description: Search across 0xinsider editorial content. - name: Insider Radar description: Suspicious trading pattern flags. - name: Events description: Durable public event replay streams. - name: Streaming description: Resumable real-time Server-Sent Events stream of live feed envelopes. - name: Webhooks description: Signed builder webhook destinations and delivery controls. - name: Usage description: Developer API budget and usage introspection. - name: System description: Health and operational status checks. - name: MCP description: Remote Model Context Protocol transport. - name: Reports description: Daily, weekly, monthly, and trader export report snapshots. externalDocs: description: 0xinsider API docs url: https://docs.0xinsider.com paths: /api/v1/whale-trades/{id}/counterparties/executions/{execution_id}/makers: get: tags: - Whale Trades summary: Page maker counterparties description: >- Returns a bounded maker-wallet page for one exact execution. Percentages keep the complete execution denominator across pages. operationId: listWhaleTradeCounterpartyMakers parameters: - name: id in: path required: true description: Whale trade ID. Accepts wt_-prefixed or raw whale_alerts.id. schema: type: string - name: execution_id in: path required: true description: Counterparty execution ID from the parent response. schema: type: string - name: snapshot_id in: query required: true description: Counterparty snapshot ID from the whale trade detail response. schema: type: string - name: cursor in: query required: false description: Opaque cursor from the previous response's next_cursor. schema: type: string - name: limit in: query required: false description: Maximum number of maker rows to return. schema: type: integer minimum: 1 maximum: 100 default: 100 responses: '200': description: Counterparty maker page content: application/json: schema: type: object required: - object - data - meta properties: object: type: string const: counterparty_maker_page data: $ref: '#/components/schemas/CounterpartyMakerPage' meta: $ref: '#/components/schemas/ResponseMeta' '400': description: >- 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. content: application/json: schema: $ref: '#/components/schemas/ApiError' '401': description: Missing or invalid API key content: application/json: schema: $ref: '#/components/schemas/ApiError' '402': description: Active Pro subscription required content: application/json: schema: $ref: '#/components/schemas/ApiError' '403': description: Account access denied content: application/json: schema: $ref: '#/components/schemas/ApiError' '404': description: Resource not found content: application/json: schema: $ref: '#/components/schemas/ApiError' '429': description: >- 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 plus RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset before any item work is done. headers: Retry-After: description: Seconds until rate limit resets. schema: type: integer RateLimit-Limit: $ref: '#/components/headers/RateLimit-Limit' RateLimit-Remaining: $ref: '#/components/headers/RateLimit-Remaining' RateLimit-Reset: $ref: '#/components/headers/RateLimit-Reset' X-RateLimit-Limit: schema: type: integer X-RateLimit-Remaining: schema: type: integer X-RateLimit-Reset: schema: type: integer X-Request-Id: schema: type: string content: application/json: schema: $ref: '#/components/schemas/ApiError' '503': description: >- 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. headers: Retry-After: description: >- Seconds until retrying is worth doing. With error.reason="read_model_warming" this is the endpoint-local read-model retry interval; without a reason it is the rate-limiter outage cooldown. Always >= 1. schema: type: integer X-Request-Id: schema: type: string content: application/json: schema: $ref: '#/components/schemas/ApiError' components: schemas: CounterpartyMakerPage: type: object required: - analysis_id - snapshot_id - execution_id - items properties: analysis_id: type: string snapshot_id: type: string execution_id: type: string items: type: array items: $ref: '#/components/schemas/CounterpartyParticipant' next_cursor: type: string nullable: true description: >- Cursor bound to the analysis, execution, last full-denominator share total, and wallet. ResponseMeta: type: object required: - request_id - cached - cost properties: request_id: type: string description: Unique request ID (req_ prefix). cached: type: boolean cache_age_s: type: integer nullable: true description: >- 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: type: integer description: >- Advisory request weight (relative compute cost). 1 for simple reads; higher for heavier endpoints. Not a credit/price. ranking_generation: type: integer nullable: true description: >- Committed PostgreSQL-owned leaderboard generation for the returned rows and cursor. Present on GET /api/v1/leaderboard; omitted on endpoints that do not read this ranking. ranking_as_of: type: string format: date-time nullable: true description: >- Authoritative RFC3339 timestamp from cache_generations.updated_at for ranking_generation. It is read in the same repeatable-read snapshot as the leaderboard rows and is not request time, cache write time, or row insertion order. directional_source: type: string enum: - live - degraded description: >- 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: type: string enum: - live - db_only description: >- 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: type: string enum: - live - partial - degraded - unavailable description: >- Whole filtered snapshot category-evidence status before pagination. Operational live always remains partial source coverage. category_skill_model_version: type: string category_skill_taxonomy_version: type: string category_skill_platform: type: string const: polymarket category_skill_scope: type: string const: observed_goldsky_primary_taker_fill category_skill_source_coverage: type: string const: partial_whale_threshold_fills category_skill_observation_started_at: type: string format: date-time category_skill_model_operationally_degraded: type: boolean description: >- 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: type: object required: - live - insufficient - stale - unknown - degraded properties: live: type: integer minimum: 0 insufficient: type: integer minimum: 0 stale: type: integer minimum: 0 unknown: type: integer minimum: 0 degraded: type: integer minimum: 0 category_skill_base_payload_hash: type: string pattern: ^[0-9a-f]{64}$ description: >- 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: type: string pattern: ^[0-9a-f]{64}$ description: >- 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. ApiError: type: object required: - object - error - meta properties: object: type: string const: error error: type: object required: - code - message properties: code: type: string enum: - bad_request - invalid_api_key - subscription_required - forbidden - not_found - account_locked - rate_limited - rate_limit_unavailable - internal_error message: type: string doc_url: type: string nullable: true param: type: string nullable: true retry_at: type: string format: date-time nullable: true description: >- The recommended next request instant (RFC3339), always in the future. Present on every retryable error: `pick_not_released`, `rate_limited`, `rate_limit_unavailable`, and `read_model_warming`. Omitted otherwise. The absolute twin of `Retry-After`; prefer the header for the sleep duration. For `pick_not_released`, the earliest of the next scheduled release, the next automatic selector attempt, the operating-window start, or about 60 seconds. See that response. reason: type: string enum: - cursor_expired - unknown_endpoint - pick_not_released - trader_not_tracked - read_model_warming - database_unavailable - idempotency_in_progress - webhook_delivery_in_progress nullable: true description: >- ADDITIVE (#7209). The specific, actionable cause behind `code`, when there is one more specific than the code itself. `code` keeps its published values, so existing clients are unaffected; new clients branch on `reason`. Omitted when the code already says everything we know. pick_not_released: no Pick of the Day is published for the current product day; schedule one request against retry_at instead of polling. unknown_endpoint: the PATH is not a route on this API -- read GET /api/v1, do not retry. trader_not_tracked: the wallet is real and the URL is right, but the trader is outside the HOT/WARM sync tiers -- stop asking for this wallet. cursor_expired: pagination went stale mid-walk -- re-request the first page and continue. 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. database_unavailable: the API's database or its connection pool is temporarily unreachable (a connection-class failure, not a query fault); code stays rate_limit_unavailable, nothing is rate-limited, retry after Retry-After / retry_at. idempotency_in_progress: retain the exact Idempotency-Key and request body, then retry shortly. webhook_delivery_in_progress: retry the URL or signing-secret configuration change after the destination's active request completes. meta: $ref: '#/components/schemas/ResponseMeta' CounterpartyParticipant: type: object required: - counterparty_key - execution_wallet - identity_status - maker_fill_count - filled_shares - filled_usdc - share_pct - match_breakdown properties: counterparty_key: type: string execution_wallet: type: string description: Lowercase Polygon wallet from the exact OrderFilled log. identity_status: type: string enum: - resolved - infrastructure - unavailable resolved_user_id: type: string nullable: true wallet_family: type: string nullable: true resolution_block: type: integer nullable: true resolution_source: type: string nullable: true display_name: type: string nullable: true grade: type: string nullable: true maker_fill_count: type: integer filled_shares: type: string description: Exact decimal shares. filled_usdc: type: string description: Exact decimal USDC amount. share_pct: type: string description: Participant share of the exact execution, from 0 through 100. match_breakdown: type: array items: $ref: '#/components/schemas/CounterpartyMatchBreakdown' CounterpartyMatchBreakdown: type: object required: - match_type - maker_fill_count - filled_shares properties: match_type: type: string enum: - COMPLEMENTARY - MINT - MERGE maker_fill_count: type: integer filled_shares: type: string description: Exact decimal shares. headers: RateLimit-Limit: description: >- Authenticated V1 per-user request limit for the current sliding window. Standard RateLimit header spelling. schema: type: integer example: 100 RateLimit-Remaining: description: >- Authenticated V1 requests remaining in the current sliding window after this response. Standard RateLimit header spelling. schema: type: integer example: 84 RateLimit-Reset: description: >- Number of seconds until the authenticated V1 request window resets. Standard RateLimit header spelling. schema: type: integer example: 42 securitySchemes: bearerAuth: type: http scheme: bearer description: >- API key authentication. Send your key in the Authorization header as `Bearer oxi_sk_live_...`. Live keys require an active Pro subscription and return live data. ````