Version selection missing from



Does anyone here maintain the site? It looks like the FIX version selector has gone away and it is stuck on FIX.5.0SP2_EP247 - English.

Prior FIX versions via fiximate

Older versions are now considered legacy - the old site with the drop down is available here:


Thanks for asking that question.FIX Version 5.0 Service Pack 2 came out more than 10 years ago and is the last of the so-called “FIX legacy versions”. Since then, there have been many Extension Packs (see that provide incremental enhancements. There is now only one “version” of FIX which is called “FIX Latest” and is enhanced by means of Extension Packs. You can always agree bilaterally to use messages and fields from higher versions even if you use e.g. FIX 4.2.

The FIX Global Technical Committee has decided to always show FIX Latest when you go to There were a number of complaints that FIXimate would not show specific extensions. The reason was that people would use a personal bookmark and not go through the FIX website. If you need to go back to one of the legacy versions, there is a link on the top left side of FIXimate called “FIXimate for legacy versions”. The direct link is and it will give you the drop down box for versions.

We have just made the change a few days ago. Please clear out your browser cache.


Ah ok. I get that it is legacy from a version standpoint, but in terms of utilization pretty much everyone in the electronic trading space for stocks and options uses something in 4.1 - 4.4 versions (sometimes borrowing parts between versions) so it’s nice to be able look through those versions. It would be like shutting down all consumers using physical cables to connect to the internet because we’ve had wireless internet for 10+ years.

I’m glad the legacy site is still around, but please don’t remove it anytime soon. I don’t foresee anyone in the electronic trading space making migrations to FIX 5.x in the near future.


You are right in terms of FIX versions when it is about (US) equities or equity options and trading between buy-side and sell-side, using tag=value syntax. FIX now supports basically all asset classes and FIX generation 5 is offered quite a bit around the world, especially by exchanges and clearinghouses. This may also be tag=value encoding but often it is FIXML or one of the binary FIX encodings (e.g. SBE). There may also be a different session layer (e.g. Websphere MQ or AMQP) in place. FIX generation 4 is about a monolithic approach for the three layer (application, presentation aka encoding, session). FIX generation 5 did not change the concepts of the application layer but gave a choice for the other two layers (to be fair, FIXML was already offered with FIX 4.4). This allows to transport FIX messages in multiple ways, not just between the classic FIX engines.

The FIX version is most important between FIX 4.2 and FIX 4.4 because of concept changes that were made back then and that FIX would no longer make these days to avoid breakage of existing applications. You can rest assured that FIX will continue to support the following application level versions (see also

  • FIX 4.2
  • FIX 4.4
  • FIX 5.0 SP2

These are the major legacy versions that are still in use. Legacy versions can be enhanced by using tags from higher versions (basically FIX Latest). This is apparently an issue for some of the FIX 4.2 users. In case of regulatory requirements, FIX has accommodated FIX 4.2 users by creating user-defined fields in the 8000 - 8499 range in addition to new tags in the standard 1 - 4999 range.

See for officially unsupported FIX legacy versions. This only means that FIX encourages users to migrate to FIX Latest or one of the supported legacy versions if the former is not possible.

As far as your example is concerned, I do not see wireless as another “version” for connecting to the internet. The situation is rather similar to asking Microsoft to support Windows XP or Word 95 to run a PC or write a document. Nobody expects these legacy software versions to be supported indefinitely. FIX as a specification written on paper is a little different from a piece of software, hence FIX continues to provide workarounds for FIX 4.2 which was published almost 20 years ago!


I have to concur with the request to keep Fiximate fully geared to support FIX versions 4.1 to 4.4.
I appreciate that a lot of work has been put into the never standards, but it doesn’t change the fact that the majority of major financial institutions (and anybody trading with them) still runs on these versions.
I doubt that making it harder to use Fiximate will push any of these institutions towards using the latest FIX version (but it might render an otherwise great tool irrelevant).



to relax your concern: At the application level, FIX is made of building blocks you are free to assemble for your needs. So having the newest version basically gives your more information and more freedom.
So you are not pushed but just free to skip information you do not need yet.

Previously, if some fields lacked, user-defined fields were put into place.
But now everybody is encouraged to use the newest FIX 5.0SP2 fields even in older versions.

I probably repeated @hanno.klein s arguments but with the exception of some special differences between FIX 4.2 and FIX 4.4 you will miss nearly nothing if you look at the latest and greatest stuff.

And the last word is said by your counter parties RoE anyway :slight_smile:

Cheers, Jörg


When using fiximate to verify a given message spec from a counterpart, you can’t really use the latest spec. Fields has been added / removed, made required or conditional. Not having the option to select the targeted FIX version is a huge loose for anyone using fiximate.

If I work with a counterpart using FIX 4.4 I do not need to see tags only available in 5.0 SP2, which the counterpart most likely is not using anyway.

This has been a great tool that I use almost daily, if the version selector is removed for good I will have to find something else.


To verify a given message from the counter party you should use the RoE of the counter party anyway.

Cheers, Jörg


While that is true, having a common starting point from FIX spec does make integrations a lot easier.

And then there are all the RoE’s out there where FIX version x.x is used, and then only a subset if the fields in messages is described, as there should not be a need to describe fields that are required by protocol.


The legacy URL is not valid anymore.


@jingz: please use the direct link for the time being. There seems to be an error with the link embedded in FIXimate which was updated just today for the publication of EP248. The link also points to FIX Latest. Apologies, will be fixed and thanks for raising the issue!


@jingz The issue with the legacy URL should be fixed but you may need to refresh your browser to get the corrected version of FIXimate.