> For the complete documentation index, see [llms.txt](https://docs.opinion.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opinion.trade/developer-guide/opinion-clob-python-sdk/builder-mode/place-order.md).

# Place Order

> Submit a signed order on behalf of a user.

## Usage (Convenience Method)

The easiest way to place an order is using the build result directly:

```python
result = builder.place_order_for_user_from_build_result(
    build_result=build_result,     # From build_order_for_signing()
    signature=signature,           # User's signature on struct_hash
    user_wallet_address="0xSafeAddress...",
)
```

### Parameters

| Parameter             | Type | Required | Description                                         |
| --------------------- | ---- | -------- | --------------------------------------------------- |
| `build_result`        | dict | Yes      | Result from `build_order_for_signing()`             |
| `signature`           | str  | Yes      | User's signature (hex string starting with `0x`)    |
| `user_wallet_address` | str  | Yes      | User's Safe wallet address (must match order maker) |

## Usage (Full Control)

For more control, pass the order fields explicitly:

```python
result = builder.place_order_for_user(
    order=build_result["order"],
    signature=signature,
    user_wallet_address="0xSafeAddress...",
    market_id=build_result["market_id"],
    order_type=build_result["order_type"],
    price=build_result["price"],
    currency_address=build_result["currency_address"],
)
```

### Parameters

| Parameter             | Type | Required | Description                                              |
| --------------------- | ---- | -------- | -------------------------------------------------------- |
| `order`               | dict | Yes      | Order struct from `build_order_for_signing()`            |
| `signature`           | str  | Yes      | User's signature (hex string starting with `0x`)         |
| `user_wallet_address` | str  | Yes      | User's Safe wallet address (must match `order["maker"]`) |
| `market_id`           | int  | No       | Market ID                                                |
| `order_type`          | int  | No       | `LIMIT_ORDER` (2) or `MARKET_ORDER` (1)                  |
| `price`               | str  | No       | Price for display                                        |
| `currency_address`    | str  | No       | Quote token address                                      |

## Response

API response dict with order details (structure depends on backend).

## Notes

* The `order["maker"]` must match `user_wallet_address` (lowercased). An `InvalidParamError` is raised if they differ.
* The signature must start with `0x`.
* Order signing uses `user.sign_hash(struct_hash)` -- see [Build Order](broken://pages/93a5a1a4b9b707b015990111262146f8c4116ee6) for details.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.opinion.trade/developer-guide/opinion-clob-python-sdk/builder-mode/place-order.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.