FIX
BitGo FIX API
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.
Capabilities
The FIX API supports the following:
- 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. You must reconnect with ResetSeqNumFlag=Y and reconcile using REST on reconnect. ResendRequest is not supported.
Downloads
- Message reference — You can download the BitGo FIX message definitions as an OpenAPI 3.0 document in JSON or YAML. The specification describes the FIX messages for your reference.
- FIX 4.4 data dictionary — You can download the BitGo QuickFIX XML dictionary as FIX44.xml. You can load this dictionary into your FIX engine to validate message fields, tags, and types.
Prerequisites
FIX API License
Your enterprise must sign a FIX API license. Contact your customer service manager (CSM) or support@bitgo.com to request access.
Access Token with FIX Scope
Create Access Token with the following scopes:
| Permission | Scope |
|---|---|
| FIX Trading API | trade_fix |
| View Trades | trade_view |
| Perform Trades | trade_trade |
Save the token in a secure place. Use this token as the Password (Tag 554) in your FIX Logon message.
Go Account Wallet ID
Use you Go Account Wallet ID as your SenderCompID (Tag 49) in every FIX message.
IP Whitelisting
ACTION REQUIRED - Before onboarding, provide your static outbound IP addresses to your BitGo CSM. Only whitelisted IPs can access the FIX service and establish a FIX session.
Note
Allow one business day for IP provisioning. If your egress IP changes after onboarding, notify your BitGo CSM immediately to avoid connectivity outages.
Connection Details
Production
| Setting | Value |
|---|---|
| Endpoint | fix.bitgo.com:5100 |
| Protocol | FIX 4.4 over TLS/TCP |
Testnet
| Setting | Value |
|---|---|
| Endpoint | fix.bitgo-test.com:5100 |
| Protocol | FIX 4.4 over TLS/TCP |
Session Types
BitGo supports two session types per enterprise, distinguished by TargetCompID:
| Session Type | TargetCompID | Purpose |
|---|---|---|
| Order Flow | BITGO |
Order submissions, cancellations, 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 delivery only on the BITGO session. The BITGO-MD session receives no order-related messages.
Maintenance Window
FIX sessions operate 24/7. Planned maintenance occurs during the following windows:
- Deployments - Monday – Friday at 01:30 – 01:50 EST. During this window the server sends a Logout with
Text="server draining, please reconnect". Reconnect immediately and a new pod accepts the connection. Reconcile open orders using 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.