Skip to main content
GET
/
api
/
orders
/
{id}
/
fills
Fills for a specific order
curl --request GET \
  --url https://core.api.dev.predictstreet.sde.adifoundation.ai/api/orders/{id}/fills \
  --header 'X-Api-Key: <api-key>'
{
  "orderId": "<string>",
  "trades": [
    {
      "id": "<string>",
      "orderId": "<string>",
      "userWallet": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb3",
      "vault": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb3",
      "marketId": "<string>",
      "price": "<string>",
      "quantity": "<string>",
      "fee": "<string>",
      "side": "buy",
      "status": "matched",
      "txHash": "<string>",
      "createdAt": "2023-11-07T05:31:56Z"
    }
  ]
}

Authorizations

​
X-Api-Key
string
header
required

Partner / integrator key — format ps_live_<keyId>_<secret>. 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 for scope taxonomy, partner kinds, rate limits, and rotation procedure.

Headers

​
X-User-Wallet
string

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.

Pattern: ^0x[a-fA-F0-9]{40}$
Example:

"0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb3"

Path Parameters

​
id
string
required

Response

200 - application/json

OK

​
orderId
string
​
trades
object[]