Skip to main content
GET
/
api
/
orders
/
{id}
Order detail
curl --request GET \
  --url https://core.api.dev.predictstreet.sde.adifoundation.ai/api/orders/{id} \
  --header 'X-Api-Key: <api-key>'
{
  "id": "<string>",
  "userWallet": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb3",
  "vault": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb3",
  "marketId": "<string>",
  "side": "buy",
  "outcome": "<string>",
  "price": "<string>",
  "quantity": "<string>",
  "filledQty": "<string>",
  "remainingQty": "<string>",
  "expiry": 123,
  "type": "limit",
  "timeInForce": "gtc",
  "status": "PENDING",
  "clientOrderId": "<string>",
  "createdAt": "2023-11-07T05:31:56Z",
  "updatedAt": "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

OK

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

"0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb3"

​
vault
string

Vault that custodies the funds / position. Equals VaultFactory.vaultOf(userWallet).

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

"0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb3"

​
marketId
string
​
side
enum<string>
Available options:
buy,
sell
​
outcome
string
​
price
string

Decimal number encoded as a string to preserve precision (e.g. '100.5').

​
quantity
string

Decimal number encoded as a string to preserve precision (e.g. '100.5').

​
filledQty
string

Decimal number encoded as a string to preserve precision (e.g. '100.5').

​
remainingQty
string

Decimal number encoded as a string to preserve precision (e.g. '100.5').

​
expiry
integer

Unix-seconds. 0 = no on-chain expiry.

​
type
enum<string>
Available options:
limit,
market
​
timeInForce
enum<string>
Available options:
gtc,
ioc,
fok
​
status
enum<string>
Available options:
PENDING,
OPEN,
FILLED,
CANCELLED,
REJECTED,
EXPIRED,
SETTLEMENT_FAILED
​
clientOrderId
string
​
createdAt
string<date-time>
​
updatedAt
string<date-time>