Products

One API for eTrading

What is it?

A client library that enables you to connect and trade on multiple FICC trading venues. We translate the various trading venue API's 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 perform an upgrade. It's a hosted service so hardware and venue connectivity issues are taken care of.


How do I get started?

  1. Register for free test access via the internet here
  2. Download the client library from Github
  3. Choose the sample code you need e.g. Download available instruments, Subscribe to Market Data, Place Orders on CLOB venues, RFQ workflow etc
  4. Add your venue credentials and select UAT or production for that venue
  5. Hit "Run"
  6. Refine your application using our UI and monitoring tools

See How You Code To Different Venues In Minutes

Which Venues are available?

Bonds
  • BGC Bonds
  • BGC GBX (BGC Trader)
  • BGC Latium (GFI)
  • Bloomberg RFQ
  • Börse Stuttgart
  • Brokertec Direct
  • Brokertec US Treasuries
  • Brokertec EU
  • Direct Match
  • Eurex Bonds
  • Euronext
  • EuroTLX
  • KCG Acknowledge
  • KCG Bondpoint
  • Liquidity Edge
  • MarketAxess
  • MOT (Borsa Italiana)
  • MTS BondsPro
  • MTS BondVision
  • MTS Cash
  • MTS Live
  • Nasdaq FI UST (ESpeed)
  • OpenBond X
  • Open Door
  • Neptune
  • TP Bonds (Elysium /Nova)
  • TradeWeb RFQ US
  • TradeWeb RFQ EU
  • TruMid
  • SGX BondPro
  • SIX Corporate Bonds
  • SIX Swiss Exchange
  • UBS Bondport

Swaps
  • BGC Lightning IRS
  • Bloomberg IRS
  • Clear Markets
  • Eris Exchange
  • ISWAP
  • TP Swapdeal
  • TradeWeb IR Swaps
    (US, EU, Asia)
  • Trad X
  • TrueEX
IR Futures
  • CME Futures and STIR
  • Eurex Bond Futures and STIR
  • Montreal Ex
  • SGX Futures
Repo
  • Brokertec Repo
  • Eurex Repo
  • MTS Repo
  • TP Repo

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…

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).

I like classes like VenueOperations, VenueNotificationsCallback, VenueStreamingNotifications a lot, giving centralised access to resources, rather than scattering it over many different services.

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