How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

SS&C Technologies Submit Order Service API

The SubmitOrderService API from SS&C Technologies — 19 operation(s) for submitorderservice.

SS&C Technologies Submit Order Service API is one of 7 APIs that SS&C Technologies publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include SubmitOrderService. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 25 operations across 19 paths, and defines 49 schemas. It is described by OpenAPI 3.2.0, at version v2026.5.0.

Requests are made against the base URL https://emsuatxapi.taltrade.com:9001.

25 operations 19 paths 49 schemas 2 DELETE5 GET14 POST4 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v2026.5.0
Base URL
https://emsuatxapi.taltrade.com:9001
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

SS&C Technologies Submit Order Service API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (Bearer). By default, every request must be authenticated.

  • Bearer — Please enter a valid token :

Paths & Operations 25

Across 19 paths, the API surfaces 25 operations — 2 DELETE, 5 GET, 14 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

SubmitOrderService 25
POST
/api/v1/order
Create api order
postApiV1Order 19 params → 200default
PUT
/api/v1/order
Replace api order
putApiV1Order 11 params → 200default
DELETE
/api/v1/order
Delete api order
deleteApiV1Order 2 params → 200default
POST
/api/v2/order
Create api order
postApiV2Order body → 200default
PUT
/api/v2/order
Replace api order
putApiV2Order body → 200default
POST
/api/v1/order/book-trade
Create api order book trade
postApiV1OrderBookTrade 4 params → 200default
POST
/api/v2/order/book-trade
Create api order book trade
postApiV2OrderBookTrade body → 200default
POST
/api/v1/order/pair-order
Create api order pair order
postApiV1OrderPairOrder 13 params → 200default
PUT
/api/v1/order/pair-order
Replace api order pair order
putApiV1OrderPairOrder 6 params → 200default
DELETE
/api/v1/order/pair-order
Delete api order pair order
deleteApiV1OrderPairOrder 2 params → 200default
POST
/api/v2/order/pair-order
Create api order pair order
postApiV2OrderPairOrder body → 200default
PUT
/api/v2/order/pair-order
Replace api order pair order
putApiV2OrderPairOrder body → 200default
POST
/api/v1/order/seed-data
Create api order seed data
postApiV1OrderSeedData 3 params → 200default
POST
/api/v2/order/seed-data
Create api order seed data
postApiV2OrderSeedData body → 200default
GET
/api/v1/order/user-accounts
Get api order user accounts
getApiV1OrderUserAccounts 1 param → 200default
POST
/api/v1/orders
Create api orders
postApiV1Orders 1 param → 200default
POST
/api/v2/orders
Create api orders
postApiV2Orders body → 200default
GET
/api/v1/order/subscribe
Get api order subscribe
getApiV1OrderSubscribe 17 params → 200default
POST
/api/v1/order/allocation-order
Create api order allocation order
postApiV1OrderAllocationOrder 10 params → 200default
POST
/api/v2/order/allocation-order
Create api order allocation order
postApiV2OrderAllocationOrder body → 200default
POST
/api/v1/order/trade-report
Create api order trade report
postApiV1OrderTradeReport 7 params → 200default
POST
/api/v2/order/trade-report
Create api order trade report
postApiV2OrderTradeReport body → 200default
GET
/api/v1/order/get-order-detail-by-date-range
Get api order get order detail by date range
getApiV1OrderGetOrderDetailByDateRange 7 params → 200default
GET
/api/v1/order/order-detail-by-order-id
Get api order order detail by order id
getApiV1OrderOrderDetailByOrderId 2 params → 200default
GET
/api/v1/order/order-detail-by-order-tag
Get api order order detail by order tag
getApiV1OrderOrderDetailByOrderTag 3 params → 200default

Schemas 49

The contract defines 49 schemas that model the data the API accepts and returns. The most detailed are OrderRow (103 properties), SubscribeOrderInfoResponse (30 properties), OrderDetailsResponse (29 properties), SubmitSingleOrderRequest (20 properties). Each schema is shown below with its type and property counts.

SubmitTradeReportRequest
object
8 properties
CancelSingleOrderResponse
object
3 properties
ChangeSingleOrderResponse
object
3 properties
ChangePairOrderResponse
object
3 properties
SubmitTradeReportResponse
object
3 properties
Google.Protobuf.WellKnownTypes.Value
object
11 properties
AllocationTypeTypesAllocation
string
SubscribeOrderInfoRequestTypesSubscriptionLevel
string
SubmitBookTradeResponse
object
3 properties
OrderDetailByDateRangeResponse
object
2 properties
AllocationDetails
object
8 properties
Google.Rpc.Status
object
3 properties
BasketOrderResponse
object
3 properties
BasketOrderRequest
object
2 properties
ChangePairOrderRequest
object
9 properties
OrderDetailByOrderIdResponse
object
2 properties
SubmitSeedDataRequest
object
3 properties
SubscribeOrderFieldOptionsTypesFields
string
AllocationType
object
1 property
OrderTypeTypesType
string
SubmitSeedDataResponse
object
3 properties
ExpirationType
object
1 property
ServerAcknowledgementTypesResponseCodesEnum
string
PriceTypeEnum
object
1 property
SubmitSingleOrderResponse
object
4 properties
Google.Protobuf.WellKnownTypes.ValueKindOneofCase
integer
SubscribeOrderInfoResponse
object
30 properties
OrderType
object
1 property
PriceTypeEnumTypesPriceTypesEnum
string
OrderDetailsResponse
object
29 properties
ServerAcknowledgement
object
4 properties
SubmitAllocationOrderResponse
object
3 properties
OrderRow
object
103 properties
Google.Protobuf.WellKnownTypes.NullValue
integer
CancelPairOrderResponse
object
3 properties
Google.Protobuf.WellKnownTypes.ListValue
object
1 property
UserAccountsResponse
object
2 properties
Google.Protobuf.WellKnownTypes.Struct
object
1 property
SubmitSingleOrderRequest
object
20 properties
Google.Protobuf.WellKnownTypes.Any
object
1 property 1 required
OrderDetailByOrderTagResponse
object
2 properties
TradeTypeTypesTypeofOrder
string
SubmitPairOrderResponse
object
3 properties
SubmitPairOrderRequest
object
16 properties
TradeType
object
1 property
ChangeSingleOrderRequest
object
12 properties
SubmitAllocationOrderRequest
object
10 properties
SubmitBookTradeRequest
object
5 properties
ExpirationTypeTypesExpirationTypes
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ss-c-technologies-submitorderservice-api-openapi.yml Raw ↑

Other APIs SS&C Technologies publishes across the network.

SS&C APIM Developer Portal
SS&C Black Diamond Wealth Platform API
SS&C Technologies Market Data Service API
SS&C Technologies User Services API
SS&C Technologies XAPI Server API
SS&C Technologies Utility Services API
Where this information came from

This is an independent, third-party profile of SS&C Technologies Submit Order Service API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.