Place Batch Orders
Place Batch Orders
POSThttps://api.gemini.com/v1/prediction-markets/order/batch
Place 1 to 20 prediction market orders in one authenticated request. The batch is synchronous and non-atomic: up-front validation rejects the entire batch, while exchange submission errors are returned per entry and do not stop later entries.
POST
curl --request POST \
--url https://api.gemini.com/v1/prediction-markets/order/batch \
--header 'Content-Type: application/json' \
--header 'X-GEMINI-APIKEY: <string>' \
--header 'X-GEMINI-PAYLOAD: <string>' \
--header 'X-GEMINI-SIGNATURE: <string>' \
--data '
{
"orders": [
{
"symbol": "GEMI-FEDJAN26-DN25",
"orderType": "limit",
"side": "buy",
"quantity": "100",
"price": "0.65",
"outcome": "yes",
"timeInForce": "good-til-cancel"
},
{
"symbol": "GEMI-FEDJAN26-DN25",
"orderType": "limit",
"side": "sell",
"quantity": "50",
"price": "0.35",
"outcome": "no",
"timeInForce": "good-til-cancel"
}
]
}
'Terms
Before sending a Prediction Markets order, check Get Terms Status. If the latest terms are not accepted, display Get Terms and call Accept Terms, then retry the batch.
Roles
The API key you use to access this endpoint must have the Trader role assigned. See Roles for more information.
The OAuth scope must have orders:create assigned to access this endpoint. See OAuth Scopes for more information.
Batch Behavior
- The complete payload is encoded and signed once.Code
- Gemini validates the batch size and every order before submitting anything. Any up-front validation, account, terms, or risk failure rejects the entire request.
- After validation, orders are submitted sequentially and results remain aligned with request order.
- An exchange rejection such as is returned in that entry's result. Other valid entries continue to be submitted.Code
Headers
Request Body
Responses
Batch processed. Results are returned in request order and may contain both successful orders and per-entry errors.
Last modified on