One API for eTrading

Connect to the whole Fixed Income market with a single integration.

One API is a client library that enables you to connect and trade on multiple FICC trading venues. We translate the trading venue APIs into the format used by TransFICC, to allow for easy/single integration – so connecting to a new venue is just a simple configuration change.

We also manage changes to APIs, when trading venues change fields or perform an upgrade. It's a hosted service so hardware and venue connectivity issues are all managed by us.

We use a client library as it provides better documentation and pre-built sample code, making connectivity easier and faster for our clients.

One API which manages the complexity shown below

This 40 second animation provides an overview of One API, including how it manages complex trading workflows.

Benefits

Application Build Icon
Simpler process to build trading applications
Quick Install Icon
Add new venues, workflows in days
Workflows Supported Icon
Improve P&L in CLOB markets
Software Releases Icon
Flexibility via daily software releases
Lower Tech Costs Icon
Lower technology costs

Easy Venue Integration Process

  1. Download the client library from GitHub
  2. Choose the sample code you need e.g. Download available instruments, Subscribe to Market Data, Place Orders on CLOB venues, RFQ workflow etc
  3. Add your venue credentials and select UAT or production for that venue
  4. Hit "Run"
  5. Refine your application using our UI and monitoring tools
  6. Contact our sales team if you wish to test the API in our lab

Our API is quick and easy to use.

Don't just take our word for it, look at this feedback from one of our clients...

Quote
"Generally speaking, everything looks very simple compared to what I'm used to.

I really like the way you made the asynchronous programming model so simple to use, with builder patterns, fluent style and centralised callback registration (e.g. you register all your callbacks in the same ClientBuilder, rather than forcing the developer to do so in the individual callbacks, in cascading fashion, which is what happens often)."