Integration Patterns

Swaps supports two integration patterns for placing prediction market orders. The chain-abstracted pattern is the core value proposition: users transact on Polymarket with any token on any chain, directly from their existing wallet — instead of needing a Polymarket trading account and pUSD. The direct pattern trades that simplicity for control over funding and order timing. Both settle on the same rails: the user’s deposit (proxy) wallet on Polygon and the Polymarket CLOB.

	Chain abstracted	Direct
Calls to place an order	1 (`getAction`)	3 (`createOrFetchPolymarketUser` → fund → `placeOrder`)
Source of funds	Any token on any chain, per order	Pre-funded deposit wallet (collateral on Polygon)
EIP-712 signature	Not required to place	Required on every trading call — see the signing guide
Order latency	Swap + order (cross-chain settlement time)	Order only — immediate against the CLOB
Best for	”Let users bet with whatever they hold”	Trading UIs with balances, repeat orders, tighter control

Pattern 1 — Chain abstracted (one call)

One getAction request with actionType=polymarket swaps any token on any chain into collateral and places the order when funds arrive. The only setup is a one-time createOrFetchPolymarketUser call your app makes behind the scenes to provision the user’s deposit wallet. Full parameter reference: Place Order (Chain Abstracted).

Pattern 2 — Direct (three steps)

The direct flow separates account setup, funding, and ordering. Once the deposit wallet is funded, orders execute immediately against the CLOB with no swap in the critical path.

Step 1 — Deploy the deposit wallet

Call POST /createOrFetchPolymarketUser with the user’s evmEoa. It returns the userId and a deposit (proxy) wallet keyed to that EOA, deploying one if it doesn’t exist yet. Check proxyWalletStatus before trading:

Status	Meaning
`ready`	Wallet is deployed and tradeable.
`deploying` / `permissioning`	Setup in progress — poll until `ready`.
`failed-deploy` / `failed-permission`	Setup failed — retry the call.
`temporary-frozen`	Wallet is frozen — call the endpoint again with `unfreeze: true` in the body.
`not-created`	No wallet yet — the call will create one.

Step 2 — Fund the deposit wallet

Fund the wallet with Polymarket collateral — pUSD on Polygon (0xC011a7E12a19f7B1f670d46F03B03f3342E82DFB, chain 137). From any other token or chain, use a standard getAction swap with the deposit wallet as the recipient:

curl "https://api-v2.swaps.xyz/api/getAction?\
actionType=swap-action&\
sender=0xB9519a08267d7B259eCA6DbD8F7286B1f176A41f&\
srcChainId=8453&\
srcToken=0x0000000000000000000000000000000000000000&\
dstChainId=137&\
dstToken=0xC011a7E12a19f7B1f670d46F03B03f3342E82DFB&\
amount=10000000000000000&\
swapDirection=exact-amount-in&\
slippage=100&\
recipient=<DEPOSIT_WALLET_ADDRESS>" \
  -H "x-api-key: $API_KEY"

Step 3 — Place the order

Call POST /placeOrder with the order details and an EIP-712 signatureByEvmEoa produced by the user’s EOA — Swaps verifies the signature and relays the order to the Polymarket CLOB. See the Polymarket Signing Guide for the typed-data schema and a working example.

After the order

Both patterns converge on the same lifecycle: track execution with GET /workflows/getStatus, then manage positions with sell, redeem, merge, and withdraw. See the Transaction Lifecycle for the end-to-end walkthrough.

Getting Started

Trading

Market Discovery

Market Information

User Positions & Activity

Pattern 1 — Chain abstracted (one call)

Pattern 2 — Direct (three steps)

Step 1 — Deploy the deposit wallet

Step 2 — Fund the deposit wallet

Step 3 — Place the order

After the order

​Pattern 1 — Chain abstracted (one call)

​Pattern 2 — Direct (three steps)

​Step 1 — Deploy the deposit wallet

​Step 2 — Fund the deposit wallet

​Step 3 — Place the order

​After the order

Pattern 1 — Chain abstracted (one call)

Pattern 2 — Direct (three steps)

Step 1 — Deploy the deposit wallet

Step 2 — Fund the deposit wallet

Step 3 — Place the order

After the order