FIX
FIX Overview
Overview
The BitGo FIX API provides a standard FIX 4.4 interface for institutional order execution and real-time market data. It supports persistent TLS/TCP sessions with heartbeat-based connection monitoring, typed message validation, and real-time fill delivery.
Supported capabilities:
- Order types: Market, Limit, TWAP, SteadyPace, Stop (stop-market and stop-limit)
- Order actions: New orders, cancellations, status queries
- Market data: Level 2 orderbook snapshots, incremental updates, subscription management
- Funding: Funded and margin orders
Session model: BitGo uses a stateless session model. Sequence numbers reset on every
connection. Clients must reconnect with ResetSeqNumFlag=Y and reconcile via REST on reconnect.
ResendRequest is not supported.
Prerequisites
FIX API License
Your enterprise must have the FIX API license enabled. Contact your BitGo account manager or BitGo support to request activation.
Access Token with FIX Scope
Create an access token with the trade_fix scope in the BitGo UI:
- Log in to the BitGo UI.
- Navigate to Developer Options → Access Tokens → Create Access Token.
- Under Permissions, select "Prime - FIX Trading API, Prime - View Trades, Prime - Perform Trades".
- Save the token securely. It will be used as the
Password(Tag 554) in your FIX Logon message.
Note: The access token is generated by you in the BitGo UI. It is not issued by BitGo support.
Access Token REST Version
Alternatively, REST API endpoints can be used to generate the access token as well: https://developers.bitgo.com/docs/get-started-access-tokens
Account ID
Your Go Account ID (32-character hex string, e.g. 0123456789abcdef0123456789abcdef) is used as
your SenderCompID (Tag 49) on every FIX message. You can find this in the BitGo UI.
IP Whitelisting
ACTION REQUIRED: Provide your static outbound IP address(es) to your BitGo account representative before onboarding. Only whitelisted IPs can access the FIX service and establish a FIX session.
Note: Allow 1 business day for IP provisioning. If your egress IP changes after onboarding, notify BitGo immediately to avoid connectivity outages.
Connection Details
Production
| Setting | Value |
|---|---|
| Endpoint | fix.bitgo.com:5100 |
| Protocol | FIX 4.4 over TCP |
Test Sandbox
| Setting | Value |
|---|---|
| Endpoint | fix.bitgo-test.com:5100 |
| Protocol | FIX 4.4 over TCP |
Session Types
BitGo supports two session types per enterprise, distinguished by TargetCompID:
| Session Type | TargetCompID | Purpose |
|---|---|---|
| Order Flow | BITGO |
Order submission, cancellation, status queries, execution reports |
| Market Data | BITGO-MD |
Orderbook snapshots, incremental updates, subscription management |
Both sessions share the same hostname and port. Your enterprise may hold one order session and one market data session simultaneously. Session type determines intended use and rate-limit scope.
Note: ExecutionReports (
35=8), OrderCancelRejects (35=9), and all order lifecycle messages are delivered only on theBITGOsession. TheBITGO-MDsession receives no order-related messages.
Maintenance Window
FIX sessions operate 24/7. Planned maintenance occurs during the following windows:
Deployments: Monday – Friday, 00:00 – 00:20 ET. During this window the server sends
Logout with Text="server draining, please reconnect". Reconnect immediately — a new pod will
accept the connection. Reconcile open orders via REST after reconnecting.
Timestamps: All timestamps are UTC, FIX 4.4 format YYYYMMDD-HH:MM:SS[.sss[sss]].
Seconds (20260415-14:30:00), milliseconds (20260415-14:30:00.123), and microseconds
(20260415-14:30:00.163512) are all accepted.