Create bulk orders
Creates multiple orders in a single request, up to 1000. Note that a successful call to this endpoint does not necessarily mean your orders have been accepted, e.g. a downstream venue might reject your order. You should therefore utilize our WebSocket APIs to listen for changes in order lifecycle events.
The response will contain an array of objects, indicating whether your order was submitted. If the order was submitted, the order_id field will be populated with the order ID assigned to this order. If the order was rejected, the reason field will be populated with the reason for rejection. The data array returned in the response object is guaranteed to be ordered in the same order as the orders you provided in the request. Again, note that even if your order was submitted, that doesn't mean it was accepted, and may still be rejected by downstream venues.
Path parameters
Account ID for the account.
Request body
Example request
{
"orders": [
{
"reference_id": "my-order-id-123",
"quantity": "100",
"price": "123.99",
"stop_price": "123.99",
"symbol": "AAPL",
"strategy": {
"min_percent": 1,
"max_percent": 35
}
}
]
}Response
Orders received. Indicates the orders were received and are pending further processing.
Example response
{
"data": [
{
"order_id": "12390213"
}
]
}Changes
Changed in 10 of the 22 revisions of this API.28930
- ▲
request property
//was restricted to a list of enum valuesrequest-property-became-enum
- ▲
the
//request property type changed from no type tostringrequest-property-type-changed
- ○
added the new
closeenum value to the request property//request-property-enum-value-added
- ○
added the new
openenum value to the request property//request-property-enum-value-added
- ▲
- ▲
removed the enum value
closeof the request property//request-property-enum-value-removed
- ▲
removed the enum value
openof the request property//request-property-enum-value-removed
- ▲
the
//request property type changed fromstringto no typerequest-property-type-changed
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ○
added the new optional request property
//new-optional-request-property
- ○
- ○
added the new
apenum value to the request property///////request-property-enum-value-added
- ○
added the new
darkenum value to the request property///////request-property-enum-value-added
- ○
added the new
povenum value to the request property///////request-property-enum-value-added
- ○
added the new
sorenum value to the request property///////request-property-enum-value-added
- ○
added the new
twapenum value to the request property///////request-property-enum-value-added
- ○
added the new
vwapenum value to the request property///////request-property-enum-value-added
- ○
- ▲
removed from the
//request propertyoneOflistrequest-property-one-of-removed
- ○
added to the
//request propertyanyOflistrequest-property-any-of-added
- ▲
- ▲
added
subschema #2to the//////request propertyallOflistrequest-property-all-of-added
- ▲
added
subschema #2to the//////request propertyallOflistrequest-property-all-of-added
- ▲
added
subschema #2to the//////request propertyallOflistrequest-property-all-of-added
- ▲
added
subschema #2to the//////request propertyallOflistrequest-property-all-of-added
- ▲
added
subschema #2to the//////request propertyallOflistrequest-property-all-of-added
- ▲
removed the enum value
apof the request property///////request-property-enum-value-removed
- ▲
removed the enum value
darkof the request property///////request-property-enum-value-removed
- ▲
removed the enum value
povof the request property///////request-property-enum-value-removed
- ▲
removed the enum value
sorof the request property///////request-property-enum-value-removed
- ▲
removed the enum value
twapof the request property///////request-property-enum-value-removed
- ▲
removed the enum value
vwapof the request property///////request-property-enum-value-removed
- ●
removed the request property
///////request-property-removed
- ●
removed the request property
///////request-property-removed
- ●
removed the request property
///////request-property-removed
- ●
removed the request property
///////request-property-removed
- ●
removed the request property
///////request-property-removed
- ●
removed the request property
///////request-property-removed
- ●
removed the request property
///////request-property-removed
- ●
removed the request property
///////request-property-removed
- ▲
- ▲
removed the enum value
gotcof the request property///////request-property-enum-value-removed
- ▲
removed the enum value
xchiof the request property///////request-property-enum-value-removed
- ▲
removed the enum value
xphlof the request property///////request-property-enum-value-removed
- ▲
- ○
added
dmadiscriminator mapping keys to the//request propertyrequest-property-discriminator-mapping-added
- ○
added the new
dmaenum value to the request property///////////request-property-enum-value-added
- ○
added the new
dmaenum value to the request property///////////request-property-enum-value-added
- ○
added the new
dmaenum value to the request property///////////request-property-enum-value-added
- ○
added the new
dmaenum value to the request property///////////request-property-enum-value-added
- ○
added the new
dmaenum value to the request property///////////request-property-enum-value-added
- ○
added the new
dmaenum value to the request property///////////request-property-enum-value-added
- ○
added the new
stop-limitenum value to the request property//request-property-enum-value-added
- ○
added to the
//request propertyoneOflistrequest-property-one-of-added
- ○
- ▲
the
///////request property type changed fromnumbertointegerrequest-property-type-changed
- ▲
the
///////request property type changed fromnumbertointegerrequest-property-type-changed
- ▲
the
///////request property type changed fromnumbertointegerrequest-property-type-changed
- ▲
the
///////request property type changed fromnumbertointegerrequest-property-type-changed
- ▲
the
///////request property type changed fromnumbertointegerrequest-property-type-changed
- ▲
the
///////request property type changed fromnumbertointegerrequest-property-type-changed
- ▲
the
///////request property type changed fromnumbertointegerrequest-property-type-changed
- ▲
the
///////request property type changed fromnumbertointegerrequest-property-type-changed
- ○
the
///////request property's max was increased from1.00to100.00request-property-max-increased
- ○
the
///////request property's max was increased from1.00to100.00request-property-max-increased
- ○
the
///////request property's max was increased from1.00to100.00request-property-max-increased
- ○
the
///////request property's max was increased from1.00to100.00request-property-max-increased
- ○
the
///////request property's max was increased from0.50to50.00request-property-max-increased
- ○
the
///////request property's max was increased from1.00to100.00request-property-max-increased
- ○
the
///////request property's max was increased from1.00to50.00request-property-max-increased
- ○
the
///////request property's max was increased from1.00to100.00request-property-max-increased
- ▲
- ●
removed the request property
//request-property-removed
- ○
added the new optional request property
//new-optional-request-property
- ○
added the new optional request property
//new-optional-request-property
- ○
added the new
stopenum value to the request property//request-property-enum-value-added
- ●