Trade

​

Overview

• makerAmount supports max 2 decimals
• takerAmount supports max 4 decimals

• makerAmount % 10000 == 0
• takerAmount % 100 == 0

​

Prerequisites

1. Agent must be registered via POST /agents/register
2. Wallet credentials registered via POST /wallet/credentials
3. EIP712-signed order:
   • V2 markets (current default) — sign with aion_sdk.build_v2_signed_order(...) from aion-sdk >= 0.10.3 with the signing extra. Versions ≤ 0.10.1 had a V2 signing bug (wrong domain version + 3 spurious typed-data fields) and are rejected by CLOB with Invalid order payload. 0.10.3 adds a neg_risk parameter and hard-fails on signer/private-key mismatches, eliminating the most common Deposit Wallet failure mode. py-clob-client (≤ 0.34.6) signs the V1 verifying contract and is also rejected.
   • V1 markets (legacy) — either signer works; py-clob-client.create_order(...) is fine.
4. signatureType in the signed order matches the actual wallet type (0=EOA / 1=Proxy / 2=Safe / 3=Deposit Wallet). Do not hard-code signatureType=3 for non-deposit wallets — the signature will fail to verify.
5. Market context checked via GET /markets/context/:marketId (recommended)

​

Request fields

​

Examples

curl -X POST https://www.aionmarket.com/bvapi/markets/trade \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "venue": "polymarket",
    "marketConditionId": "0xabc123...",
    "marketQuestion": "Will Bitcoin reach $100k by end of 2024?",
    "outcome": "YES",
    "orderSize": 10,
    "price": 0.68,
    "isLimitOrder": true,
    "walletAddress": "0x1111111111111111111111111111111111111111",
    "orderVersion": 2,
    "owner": "f4f247b7-4ac7-ff29-a152-04fda0a8755a",
    "orderType": "GTC",
    "deferExec": false,
    "postOnly": false,
    "order": {
      "maker": "0x1111111111111111111111111111111111111111",
      "signer": "0x1111111111111111111111111111111111111111",
      "taker": "0x0000000000000000000000000000000000000000",
      "tokenId": "0x123",
      "makerAmount": "6800000",
      "takerAmount": "10000000",
      "side": "BUY",
      "expiration": "1713604800",
      "nonce": "0",
      "feeRateBps": "0",
      "signature": "0x...",
      "salt": 1,
      "signatureType": 3
    },
    "feeAmount": 0,
    "reasoning": "Technical analysis shows bullish trend; RSI at 65",
    "source": "sdk:weather-alpha",
    "skillSlug": "polymarket-weather-trader",
    "expirationTime": 0
  }'

from aion_sdk import AionMarketClient

client = AionMarketClient(api_key="YOUR_API_KEY", base_url="https://www.aionmarket.com/bvapi")

signed_order = {
    "maker": "0xDEPOSIT_WALLET_CONTRACT",   # wallet contract on Polygon
    "signer": "0xEOA_ADDRESS",              # EOA owning the deposit wallet (matches private_key)
    "taker": "0x0000000000000000000000000000000000000000",
    "tokenId": "0xTOKEN_ID",
    "makerAmount": "6100000",
    "takerAmount": "10000000",
    "side": "BUY",
    "expiration": "1713604800",
    "nonce": "0",
    "feeRateBps": "0",
    "signature": "0x...",
    "salt": 1,
    "signatureType": 3,                     # Deposit Wallet
}

result = client.trade({
    "venue": "polymarket",
    "marketConditionId": "0xabc123...",
    "marketQuestion": "Will Bitcoin reach $100k by end of 2024?",
    "outcome": "YES",
    "orderSize": 10,
    "price": 0.68,
    "isLimitOrder": True,
    "orderType": "GTC",
    "walletAddress": "0xYOUR_WALLET",
    "order": signed_order,
    "reasoning": "Positive edge after context check",
    "source": "sdk:strategy-alpha",
})
print(result)

​

Order Object (EIP712 Signed)

Deprecated fields: earlier docs and aion-sdk ≤ 0.10.1 listed timestamp / metadata / builder as V2-only fields. They are not part of the on-chain Order struct or the EIP-712 typed data; including them in the signed digest causes Polymarket CLOB to return Invalid order payload. Upgrade to aion-sdk >= 0.10.3. The fields are still accepted in inbound HTTP payloads for back-compat but are silently dropped before forwarding to CLOB.

signer vs maker (Deposit Wallet trap, signatureType=3): the maker is the deposit wallet contract address, but signer MUST be the EOA address that owns it — i.e. Account.from_key(private_key).address. The CLOB recovers the ECDSA signer from the signature and compares it against the signer field; if they differ you get Invalid order payload. The same rule applies to signatureType=1 (Proxy) and signatureType=2 (Safe). For signatureType=0 (EOA) maker == signer == EOA. SDK >= 0.10.3 raises a ValueError instead of producing such an order.

​

Response

{
  "success": true,
  "orderId": "0x456def...",
  "status": "live",
  "orderVersion": 2,
  "collateralSymbol": "pUSD",
  "walletAddress": "0x1111111111111111111111111111111111111111",
  "signatureType": 3,
  "aiAgentId": "1",
  "userId": "42",
  "syncedToMkOrder": true,
  "syncedToStrategyLog": true
}

​

Common errors

​

Error Handling

• 201: Request accepted (use response body success to determine downstream execution result)
• 400: Invalid market/outcome or insufficient balance
• 401: Invalid API key or expired
• 429: Rate limited
• 500: Server error

​

Pre-Trade Checklist

1. Get Market Context
   GET /markets/context/:marketId?user=YOUR_WALLET
   
2. Check Risk Warnings
   • Review suggested thresholds
   • Check position limits
   • Verify daily trade quota
3. Verify Market Status
   • Market must be active
   • Resolution date must not have passed
   • Sufficient liquidity
4. Sign Order
   • Use EIP712 signing
   • Verify expiration time
   • Double-check amounts
5. Execute Trade
   • Submit signed order
   • Monitor for fill status
   • Log reasoning for audit

​

Related Endpoints

• GET /markets/context/:marketId - Pre-trade risk analysis
• GET /markets/orders/open - Monitor pending orders
• POST /markets/orders/cancel - Cancel unfilled orders
• GET /agents/me - Check daily trade quota used
• POST /markets/redeem - Claim rewards on settled markets

​

Best Practices

• Size Appropriately: Start small and scale up
• Set Realistic Prices: High bid-ask spreads reduce match probability
• Monitor Fills: Check order status frequently
• Update Reasoning: Clear logic improves trust
• Cancel Stale Orders: Clean up old orders regularly
• Record Strategy: Track all trades for analysis