Launch a FIX API

How to add FIX connectivity to an existing platform

You already offer REST & Websocket, but your institutional clients ask for FIX. We design the API, write the spec and train your team.

All for a fixed price.


FIX is a design project, not a port

You already run a REST and WebSocket API that works. Adding FIX looks like a translation job, and that is where most first FIX APIs go wrong.

FIX is a stateful session. It has its own rules for sequence numbers, resends, order state and cancel-replace chains, and none of them has an equivalent in REST. The choices you make in the first few weeks decide how long every client takes to connect for years afterwards.

FixSpec has worked on FIX APIs with exchanges and trading venues since 2012., and our founders have been writing FIX specifications for almost three decades.

Phase 1:

The Launch Project

Your professional FIX API designed by deep domain experts.

Fixed price projects, starting at £15,000.

  • API design. We map your existing REST and WebSocket functions onto FIX messages, fields and workflows, and tell you where they do not map cleanly.
  • A spec your clients can code to. Every message, field, enumeration and conditional rule, written by people who write FIX specs for a living. You own it as a machine-readable file, with a branded PDF and a QuickFIX dictionary generated from it.
  • Team training. For your engineers, product and support staff, built around your own API and not a generic course.
  • Engine selection. Independent advice on which FIX engine suits your stack.
  • Onboarding design. The test scenarios each client should pass before trading.

Phase 2:

Production Launch

Optional production support and tooling (annual license).

  • FIX docs beside your developer portal. Interactive and searchable, under your brand, on your own sub-domain. Your REST docs stay where they are.
  • Client self-certification. Clients connect to your test environment and work through the scenarios. Rules decide pass or fail, and your team approves the result. Nobody reads logs by hand.
  • A record of who is certified for what, and against which version of the spec.
  • Ready for AI coding agents. Your clients’ developers increasingly hand the spec to an AI. A structured spec, llms.txt and a Markdown version of every page give it rules to follow in place of tables to guess from.

FixSpec Labs accelerated our time to market in delivering a best-in-class FIX connectivity solution. Thanks to their expertise and support, we seamlessly onboarded our institutional clients to FIX who now happily execute millions of orders through Bullish.

Sandeep Rakhra, Engineering Director, Bullish

Step 1

Scoping Call

Understanding your market model and objectives. Map project plan and team contacts.

Step 2

Iterative Design

Message mapping, session behaviour and workflows. Regular review & approval checkins.

Step 3

Documentation

API document delivery in Word (requirements), developer portal (customers) and QuickFIX (configuration).

Step 4

Operational Training

Monitoring and supporting FIX is different to REST. We train your team and help craft processes.

Step 5

First Client Connects

By your side as the first client connects and conforms, working alongside you to refine and automate.

Frequently Asked Questions

We already have a developer portal for REST. Do we have to move?

Not necessarily. We are the only portal which natively supports REST and FIX, but if you want to add a FIX-only portal alongside your existing portal, that’s fine. It would have it’s own sub-domain and carry your logo and colours.

Our engineers know QuickFIX. Why not write the spec ourselves?

A QuickFIX dictionary lists messages and fields. It does not say which fields are required for which order type, what you send back, or how your session behaves. Those are the parts clients get wrong.

Do you build or supply the FIX gateway?

No, we are completely agnostic to FIX engine. We supply the design blueprint that your engineers build against. We can advise on the engine to choose and check your implementation, however, if that helps.

Do we need to fully automate certification from day one?

Sometimes, there is value in doing the first couple manually as you work through the kinks and gain experience. Manually checking each client by reading logs simply doesn’t scale; what works for the first two clients will not work for twenty. Start small and add certification automation before the big wave of clients hit.

Which FIX version should we use?

We can recommend one in the scoping call, based on the asset class and workflows you would like to support. The golden rule, however, is that newer FIX versions aren’t “better” than older versions.