Sway Charts API Documentation
  • REST API Specification
    • Getting Started
      • Introduction
      • Errors
      • API Versioning
      • Conditional Requests & Updates
      • Entity Versioning
      • Data Types and Formats
      • Rate Limits & Throttling
    • Authentication & Authorization
      • HMAC Authentication
      • POST Create Session Token
      • POST Ping
      • POST Logout
    • Trading
      • POST Place Order
      • PUT Modify Order
      • DELETE Cancel Order
    • Reference Data
      • GET List Instruments
      • List Instrument Details
    • Users and Accounts
      • GET Get Users
      • GET List Account Portfolio
      • GET List Open Positions
      • GET List Open Orders
      • GET List Cash Transfers
      • GET POST List Orders
      • GET List Account Metrics
      • GET List Account Events
    • Market Data
      • POST Request Market Data
    • Conversion Rates
      • POST Get Conversion Rates
    • Cash Transaction
      • Single Order Request
      • Order Group Request
      • Order Response
      • Instrument
      • Instrument Details
      • Trading Session
      • Limit Value
      • Margin Rate
      • Margin Tier
      • User Details
      • Account Details
      • Account Portfolio
      • Balance
      • Position
      • Order
      • Order Leg
      • Execution
      • Cash Transfer
      • Historic Order List
      • Account Metrics
      • Position Metrics
      • Currency Metrics
      • Account Event
      • Market Data Request
      • Market Data Event Type
      • Market Data List
      • Quote
      • Candle
      • Conversion Rate
    • Revision History
Powered by GitBook
On this page
  1. REST API Specification
  2. Trading

POST Place Order

PreviousTradingNextPUT Modify Order

Last updated 1 year ago

POST https://api.swaycharts.io/dxsca-web/accounts/{account code}/orders

Places an order or a group of orders on an account

The API allows submitting a new order or a group of orders on an account. Users can always issue orders on their own accounts, but can only issue orders on behalf of other accounts if the corresponding permissions are configured.

The API is via POST, so it's not idempotent. To avoid issues with duplicate orders, a client is expected to submit a client-unique id of an order with the request. This id is used to track the order later on. .

// Request

Single Order Request or Order Group Request

Authorization header should be included in case of basic authentication
// Path Parameters

accountCode - unique code assigned to an account (URL-encoded, https://en.wikipedia.org/wiki/Percent-encoding). See account code
// Errors

Common errors

API is not permitted for the user or account with the given id doesn't exist or account with the given id is not accessible for the user

Status code: 404 Not Found
Error code: 2
Description: Entity not found at server
Order request or order group is not well-formed or is semantically incorrect (e.g. limit order doesn't have price or order group includes both OCO and Contingent fields)

Status code: 400 Bad Request
Error code: 33
Description: Incorrect request (<details about an error>)
Order didn't pass pre-issue checks

Status code: 409 Conflict
Error code: <various>
Description: <various>
Order with such a client order id already exists in the system

Status code: 409 Conflict
Error code: 100
Description: Order with this id already exists (<client order id>)
Client order id is invalid (see client ids)

Status code: 400 Bad Request
Error code: 101
Description: Client-originated identifier is not valid
See client ids