An event raised when one or more of the fields sent in a client event are invalid.
An event raised when a client event would trigger an invalid state transition on the trade model.
Trades are comprised of one or more trade legs, each representing the exchange of a financial instrument and the resultant cashflow.
The LegAction interface represents a change to the legs that make up a trade.
A single Trade active in the system.
An open trade messaging communications channel with an end user.
Provides notifications relating to the
A single event acting on a Trade.
Used to receive TradeEvents from the system.
All Trading DataSource applications must create an instance of this class.
An enumeration of possible actions that can be performed on a leg.
Used for all errors raised by the Trading DataSource, or raised by user code that needs to notify the Trading DataSource of an exception during a callback.
The Caplin Trading Integration API provides Java classes and interfaces that allow you to create Trading Adapters.
A Trading Adapter sits between Caplin Liberator and an external trading system, handling the trade messages that flow between Caplin Platform client applications and the trading system when an end-user trades.
The Trading Integration API is built on top of the
Caplin DataSource for Java API (package
and its subpackages). It allows
Trading Adapters to communicate with Liberator using the
DataSource protocol, but without the need to write code at the DataSource
For additional information about how to use this API, see the following resources: