Click to Show Menu

FIX FAQs

Why are FIX API reports received from the server duplicated?

FIX API reports will be duplicated if you have multiple connections to the API open simultaneously. The server will send a copy of the FIX response to each active connection.

Why is there no HeartBeat response for the QUOTE feed?

This is expected behavior. When quotes are streaming, it negates the need for the heartbeat to be sent.

Is it possible to receive non-aggregated depth of market?

Unfortunately the answer is no, tag 266 is not included in our rules of engagement. To support this it would require a complete overhaul of how the industry works. Spotware receive aggregated prices from brokers, meaning this possibility requires a change to made further upstream. Furthermore due to the contractual agreements and competition brokers are unlikely to want to disclose their liquidity sources. If a broker has good sources, every other broker is going to want to know how, meaning they loose their competitive edge.

I send a FIX message but I receive no response. Why?

If your message is not a valid FIX message, the server will not respond to it. You can check the validity of your FIX message using a FIX Parser
e.g. https://fixparser.targetcompid.com. Other issues that your message might have are the below

  • The credentials you have provided are not valid. Check your host, port, trading account number, password, SenderCompID, TargetCompID and SenderSubID .
  • Your checksum calculation is wrong.
  • The DateTime is not in UTC.
  • Tags are missing. Refer to the Rules of Engagement for the required tags.
  • Tags are in the wrong order. Refer to the Rules of Engagement for the correct order of the tags.