GuidesAPI Reference
DocumentationLog In

Connectivity

FIX (Financial Information eXchange) is a standard protocol which can be used to enter orders, submit cancel requests, and receive fills. FIX API users typically have existing software that runs FIX for order management. Users who are not familiar with FIX should consider using the REST API.

Endpoint: tcp+ssl://fix.exchange.coinbase.com:4198

πŸ“˜

Resend requests are not supported. Every connection establishes a new session and a new set of session sequence numbers.

Connectivity

Before logging onto a FIX session, clients must establish a secure connection to the FIX gateway (fix.exchange.coinbase.com:4198).

TCP SSL

If your FIX implementation does not support establishing a native TCP SSL connection, you must setup a local proxy such as stunnel to establish a secure connection to the FIX gateway. See the SSL Tunnels section for more details and examples.

Static IP

Coinbase Exchange does not support static IP addresses. If your firewall rules require a static IP address, you must create a TCP proxy server with a static IP address which is capable of resolving an IP address using DNS.

AWS IP

If connecting from servers outside of AWS which require firewall rules, use the AWS provided resources to determine how best to whitelist AWS IP ranges.

πŸ“˜

Changes are deployed every Monday and Thursday at or near 11 AM PST. At that time, a logout message is sent from the server to indicate the session is ending. We do not deploy on US federal holidays.

Best Practices

To optimize your FIX set up, spread traffic over as many portfolios as possible to minimize order-entry latencies.

You should configure:

  • Maximum of 25 portfolios (or profiles)
  • Maximum of 7 sessions per portfolio
  • 1 API key per session to guarantee a connection

There is a rate limit of 50 requests per rolling second per session. See: Rate Limits.

πŸ“˜

Rolling second: the clock starts when the first command is sent. We use a lazy-fill token bucket implementation.