Connectivity

FIX API

OptAxe builds to your existing FIX specification for pricing. All RFQs are priced within your own risk systems.

Session

How the session is configured

Configuration

  • Protocol version: FIX 4.4, the standard message set for OTC FX and FX options connectivity. The venue's message specification and any extensions are issued to participants during onboarding.
  • Session structure: a single FIX session per firm carries axes, quote requests, quotes and execution reports. A separate drop copy session is available on request for risk and compliance.
  • Transport: TLS on all connections, with IP allow-listing per firm. A site-to-site VPN can be arranged where a firm's policy requires it.
  • Instrument identification: currency pair, expiry, strike, call or put, and notional currency. Multi-leg structures are sent as a single request, with each leg carried in the standard FIX legs repeating group, so the structure is priced as one package.
The full FIX specification, including the message set, session configuration and certification steps, is issued to participants and applicants during onboarding.

Integration

From first call to production

1

Specification review

Your connectivity team receives the specification and maps it against your pricing engine's existing FIX.

Owner: participant, with OptAxe support

2

Test connectivity

Session established to the UAT environment; logon, heartbeat and resend verified.

Owner: participant

3

Certification

Scripted flows for axe lifecycle, quote request and response, execution and drop copy.

Owner: OptAxe

4

Production

Production credentials issued; first day supported live by a named OptAxe contact.

Owner: both

Request the FIX specification

Available to participants and certified vendors under the participant or partner agreement.

OnboardingContact