Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/bullish-exchange/api-docs/llms.txt

Use this file to discover all available pages before exploring further.

The Bullish Exchange FIX API enables high-performance, low-latency order management and trade execution using the industry-standard Financial Information eXchange (FIX) protocol. It is purpose-built for institutional trading workflows that require deterministic, reliable connectivity with minimal overhead.
The FIX API is available to institutional clients only and is exclusively accessible through private network connectivity — either AWS PrivateLink or GCP Private Service Connect. Direct public internet access is not supported.

Private Connectivity Options

Because the FIX API is not exposed to the public internet, you must establish a private network connection before you can connect. Bullish supports two private connectivity methods:

AWS PrivateLink

AWS PrivateLink provides private connectivity between your VPC and the Bullish FIX service endpoint without exposing your traffic to the public internet. Bullish will provide the published service IDs required to establish the connection. Once the PrivateLink connection is successfully established, you will be able to connect to the Bullish FIX service endpoint.

GCP Private Service Connect

GCP Private Service Connect allows you to access the Bullish FIX managed service privately from inside your VPC network. Bullish will provide the published service IDs required to establish the connection. Once the Private Service Connect connection is successfully established, you will be able to connect to the Bullish FIX service endpoint.

Connectivity Recommendations

For GCP deployments, the most optimal connection is to operate within the asia-southeast1-a Availability Zone. Note that this may change at any time and without warning to another Availability Zone within asia-southeast1 for operational reasons.
For AWS or GCP connectivity details and to obtain your published service IDs, contact your Bullish sales representative.

Getting Started

1

Contact Your Sales Representative

Reach out to your Bullish sales representative to confirm institutional client eligibility and to receive the published service IDs for either AWS PrivateLink or GCP Private Service Connect.
2

Establish Private Connectivity

Use the service IDs provided by Bullish to create your PrivateLink endpoint (AWS) or Private Service Connect endpoint (GCP) within your VPC. Verify the connection is active before proceeding.
3

Review the FIX Specification

Review the latest Bullish FIX Protocol Specification (v1.0.13) and the FIX Dictionary XML from the FIX API specs repository to understand message types, fields, and session management requirements.
4

Connect and Test

Use your FIX engine to connect to the Bullish FIX service endpoint over your established private connection. Test with the sandbox environment before going live.

FIX Protocol Specifications

The current specification is Bullish FIX Protocol Specification v1.0.13. All versions (v1.0.2 through v1.0.13) and the FIX Dictionary XML are available in the GitHub repository.

FIX API Specs Repository

Browse all FIX Protocol Specification PDFs (v1.0.2–v1.0.13) and the FIX Dictionary XML file in the official Bullish API docs repository.

Build docs developers (and LLMs) love