> ## Documentation Index > Fetch the complete documentation index at: https://docs.testnet.dev.adipredictstreet.com/llms.txt > Use this file to discover all available pages before exploring further. # Fills for a specific order > All trades that filled against the given `orderId`, in execution order. Returns `200 {orderId, trades: []}` for an order with no fills (PENDING / OPEN / unfilled CANCELLED) AND for nonexistent IDs — empty `trades` is not a 404 signal. To distinguish, use `/api/orders/{id}` (returns 404 for unknown IDs). ## OpenAPI ````yaml /api-reference/openapi.json get /api/orders/{id}/fills openapi: 3.1.0 info: title: PredictStreet core-api description: >- Client-facing HTTP gateway for the PredictStreet prediction-market platform. This spec is hand-written against the NestJS controllers and DTOs in core-api/src/modules/. For the source-of-truth live spec, run `./scripts/pull-openapi.sh` against a running core-api (NestJS exposes it at /api/docs-json). **Partner kinds.** Every authenticated endpoint resolves a request's *effective wallet* from the partner row. `single_wallet` partners bind to one `associatedWallet` set at creation. `multi_wallet` partners declare the actor on every request via an `X-User-Wallet: 0x<40-hex>` header. See the [Partner kinds](/auth/api-keys#partner-kinds) doc for the full contract. version: '2026-06-16' contact: name: PredictStreet partners email: partners@predictstreet.com servers: - url: https://core.api.dev.predictstreet.sde.adifoundation.ai description: Testnet (partner integrator API — final domain TBD) security: [] tags: - name: Deposits description: >- Gasless USDC deposit relay - submit a signed EIP-2612 permit and the platform broadcasts the on-chain deposit for you (no gas). - name: Events description: >- Polymarket-style event grouping with football metadata (group, stage, teams, tags). - name: Tags description: Curated tag taxonomy used to filter events. - name: Markets description: 'Public market data: list, detail, orderbook, trades, OHLC.' - name: Orders description: >- Signed-order place / cancel / read. Requires `X-Api-Key` with `orders:read` / `orders:write` scope; every write additionally requires an EIP-712 signature over the order. - name: Portfolio description: >- Balances, positions, trades, fees, vault info for the key's `associatedWallet`. Requires `X-Api-Key` with `portfolio:read` scope. - name: Matches description: >- admin.matches aggregate — groups several events into one fixture/card (1X2 + first-scorer + over-under under one matchup). - name: Vault description: >- Backend co-signatures for ERC-1155 split / merge, and recovery for off-chain locks when the corresponding chain tx never confirmed. Requires `X-Api-Key` with `vault:write` scope plus an EIP-712 signature over the operation. - name: Leaderboard description: Public ranked leaderboard across PnL / volume buckets. - name: Search description: Global search across users, events, and matches. - name: Withdrawal Security description: >- Self-service withdrawal 2FA (TOTP) and withdrawal-address whitelist. Same endpoints serve the frontend (Privy JWT) and API-key integrators. Mutations need `vault:write`, reads `portfolio:read`. Both are opt-in per wallet and only gate withdrawals once the platform enables withdrawal-security enforcement. paths: /api/orders/{id}/fills: get: tags: - Orders summary: Fills for a specific order description: >- All trades that filled against the given `orderId`, in execution order. Returns `200 {orderId, trades: []}` for an order with no fills (PENDING / OPEN / unfilled CANCELLED) AND for nonexistent IDs — empty `trades` is not a 404 signal. To distinguish, use `/api/orders/{id}` (returns 404 for unknown IDs). operationId: OrdersController_fills parameters: - name: id in: path required: true schema: type: string - $ref: '#/components/parameters/UserWalletHeader' responses: '200': description: OK content: application/json: schema: type: object properties: orderId: type: string trades: type: array items: $ref: '#/components/schemas/Trade' security: - ApiKeyAuth: - orders:read components: parameters: UserWalletHeader: name: X-User-Wallet in: header required: false description: >- **Required for `multi_wallet` partners on every authenticated request; ignored for `single_wallet`.** Declares the acting end-user wallet for this request — drives KYC checks, balances/positions/orders attribution, rate-limit buckets, and audit. Lower-cased server-side. Missing on a multi_wallet key → 401 `api_key_user_wallet_required`; malformed → 401 `api_key_user_wallet_invalid`. The on-chain `CTFExchange`/`Vault` contracts still verify EIP-712 signer ↔ vault binding, so loosening API-layer attribution is safe by construction. schema: $ref: '#/components/schemas/EthereumAddress' example: '0x1234567890abcdef1234567890abcdef12345678' schemas: Trade: type: object properties: id: type: string orderId: type: string userWallet: $ref: '#/components/schemas/EthereumAddress' description: EOA that signed the order on this side. vaultAddress: $ref: '#/components/schemas/EthereumAddress' description: >- Vault that custodies the funds / position for this side. Equals `VaultFactory.vaultOf(userWallet)`. marketId: type: string price: $ref: '#/components/schemas/DecimalString' quantity: $ref: '#/components/schemas/DecimalString' fee: $ref: '#/components/schemas/DecimalString' side: type: string enum: - buy - sell status: type: string enum: - matched - settlement_pending - settled description: >- Trade lifecycle. `matched` — matcher confirmed the cross, chain-side submission may not have started yet. `settlement_pending` — match-submitter broadcast the on-chain tx (`txHash` populated); awaiting chain confirmation. `settled` — chain confirmed and balances/positions mirrored off-chain. The `settlement_failed` ops-only state is filtered out of the public feed. txHash: type: string nullable: true pattern: ^0x[0-9a-fA-F]{64}$ description: >- On-chain settlement tx hash. Populated when the match-submitter broadcasts (status flips to `settlement_pending`). `null` for `matched` rows that have not yet been submitted. settledAt: type: string format: date-time nullable: true description: >- ISO-8601 timestamp of the chain settlement-confirmation event. `null` while `status !== 'settled'`. adjustment: type: string enum: - NONE - MINT - BURN default: NONE description: >- Chain-side classifier the matcher attaches at fill time (BR-MC-BIN-01). `NONE` — standard token-for-cash swap (default). `MINT` — both buyers, `splitPosition` minted a complete set. `BURN` — both sellers, `mergePositions` redeemed a complete set back to USDC. Always `NONE` on non-binary markets and on binary trades where both sides shared the same outcome. createdAt: type: string format: date-time EthereumAddress: type: string pattern: ^0x[a-fA-F0-9]{40}$ example: '0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb3' DecimalString: type: string description: >- Decimal number encoded as a string to preserve precision (e.g. `'100.5'`). securitySchemes: ApiKeyAuth: type: apiKey in: header name: X-Api-Key description: >- Partner / integrator key — format `ps_live__`. Issued by PredictStreet ops via the admin panel; never self-service. Never ship to a browser. `multi_wallet` partners must additionally send `X-User-Wallet: 0x<40-hex>` on every authenticated request to declare the acting wallet. See the [API keys guide](/auth/api-keys) for scope taxonomy, partner kinds, rate limits, and rotation procedure. ````