> ## Documentation Index
> Fetch the complete documentation index at: https://docs.b3os.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Polymarket Place Bet (Batch)

Submit multiple orders atomically in a single CLOB request. All orders land on the orderbook simultaneously — no price drift between legs. Ideal for: arbitrage strategies, multi-leg hedges, portfolio rebalancing, event-based multi-market bets.

![Polymarket Place Bet (Batch) logo](https://cdn.b3.fun/b3os-icons/polymarket-icon.png)
Catalog action EVM Onchain wallet

Submit multiple orders atomically in a single CLOB request. All orders land on the orderbook simultaneously — no price drift between legs. Ideal for: arbitrage strategies, multi-leg hedges, portfolio rebalancing, event-based multi-market bets.

**Review wallet and value movement**

This action can require a wallet connector, gas, token movement, or an external side effect. Test with simulation or a controlled amount before using it in a live workflow.

## At a Glance

| Field | Value |
| --- | --- |
| Action ID | `polymarket-place-bet-batch` |
| Category | EVM Onchain |
| Connector | `wallet` |
| Requires gas | No |
| Funds movement | None declared |
| Tags | `polymarket`, `trading`, `batch`, `arbitrage`, `write` |

## Payload Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `orders` | `array` | Yes | Array of orders to submit atomically |
| `orderType` | `string` | No | Order type for all orders in the batch. GTC \(Good Till Cancelled\), GTD \(Good Till Date\), FOK \(Fill Or Kill\), FAK \(Fill And Kill\). |
| `postOnly` | `boolean` | No | Post-only mode — all orders are placed as maker orders only. If any would immediately match, it is rejected instead of filling as a taker. |
| `deferExec` | `boolean` | No | Defer execution — orders land on the book simultaneously but matching is deferred. Useful for atomic multi-leg strategies. |

## Result Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `orders` | `array` | Yes | Array of order results |
| `batchSize` | `number` | Yes | Number of orders submitted in the batch |
| `submittedAt` | `string` | No | ISO timestamp when the batch was submitted |

## Examples

**Workflow node**

```json
{
  "type": "polymarket-place-bet-batch",
  "payload": {
    "orders": [
      {
        "tokenId": "1",
        "side": "BUY",
        "price": 0.5,
        "size": 1
      }
    ]
  },
  "children": [],
  "connector": {
    "type": "wallet",
    "id": "conn_wallet"
  }
}
```
  **Test with API**

```bash
curl -X POST "https://api.b3os.org/v1/actions/polymarket-place-bet-batch/test" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "inputs": {
    "orders": [
      {
        "tokenId": "1",
        "side": "BUY",
        "price": 0.5,
        "size": 1
      }
    ]
  }
}'
```

**Use expressions for dynamic values**

Payload fields can use workflow expressions such as `{{$trigger.body.amount}}`, `{{$nodes.fetch.result.price}}`, and `{{$props.asset}}` when the value should come from a trigger, prior node, or reusable workflow prop.