Overview
Predexon Trading API manages wallets on behalf of accounts. Instead of handling private keys, gas, or transaction signing, the API handles all of that automatically.Simplified Integration
No wallet SDKs or key management needed in your application
No Gas Management
All transaction fees are handled by the platform
Secure Key Management
Private keys are securely managed - you never handle them
How It Works
- Your application calls the Predexon Trading API
- Predexon API manages account wallets and executes trades
- Venues settle transactions on their respective chains (Polygon for Polymarket, BSC for Predict and Opinion, Base for Limitless, HyperCore for Hyperliquid)
Wallet Management
On the/api/accounts path, wallet provisioning is two-stage:
- Account creation (
POST /api/accounts/create) - provisions the deposit wallet (a Base USDC address) and the underlying trading identity. The deposit wallet is the single entry point for funds; access it via Get Deposit Info ordepositWallet.addresson Get Account. - Venue enablement (
POST /api/accounts/{accountId}/enable) - configures the account for a specific venue: on-chain approvals, CLOB credentials (Polymarket), Safe setup (Opinion). Required per venue you want to trade on.
| Venue | Chain | Collateral |
|---|---|---|
| Polymarket | Polygon | pUSD (Polymarket USD) |
| Predict.fun | BSC | USDT (BEP-20) |
| Opinion | BSC | USDT (BEP-20) |
| Limitless | Base | USDC (native) |
| Hyperliquid | HyperCore | USDH (USDC-pegged) |
address once it reaches status: "active". The deposit wallet is a distinct on-chain address from any venue trading wallet.
Key Security
Private keys are managed by Turnkey, a secure, hardware-backed key management infrastructure:- Predexon never has access to private keys - keys are generated and stored in Turnkey’s secure enclaves
- Hardware-backed security - keys never leave the enclaves
- No key management in your app - all signing happens server-side
Market Identification
On the accounts path, every order or redeem request identifies a market with amarket bag containing the venue-specific fields the target venue requires (tokenId, marketId, outcome, assetId, marketSlug). Required fields differ by venue — see the Place Order reference for the per-venue matrix.
Order Execution
All venues use an orderbook model with limit and market orders. Order types:- Limit orders - rest on the orderbook at a specific price until matched.
- Market orders - execute immediately at the best available price.
- Orders can be partially filled.
- Open orders can be cancelled.
- Response
statusis normalized across venues:open,filled,cancelled,expired,pending,failed.
Position Lifecycle
Redeemable
Winning positions are redeemed via Redeem Position for payout in the venue’s stablecoin.
Security Model
Each API key can only access accounts it created. Attempting to access another API key’s account returns403 Forbidden.
Comparison to Self-Custody
| Feature | Predexon | Self-Custody |
|---|---|---|
| Key management | Handled by API | You manage |
| Transaction fees | Handled by the platform | You pay |
| Integration complexity | REST API calls | Wallet SDKs + signing |
| Multi-chain support | Unified API | Separate integrations |
| Withdrawal | API call | Direct blockchain tx |
Best Practices
Store account IDs
Save the
accountId returned by Create Account - it’s required for every subsequent call.Enable venues explicitly
Call Enable Venue for each venue the account should trade on, and poll Get Account until the venue’s
status is active.Check balance before orders
Always verify available funds with Get Balance before placing orders.
Next Steps
Funding & Withdrawals
Fund venues via the deposit wallet, then withdraw to any supported chain
Placing Trades
Order types, venues, and the full trading workflow
Fees & Monetization
Set up partner fees to earn revenue
Continue learning
Previous: Smart Money
Wallet classification and signal anatomy.
Next: Custody & Key Management
The deeper dive on the security model behind managed wallets.