One price feed, multiple ways to connect.

Simple streaming over TCP

The shortest integration path is a plain, line-based price stream. After a small login handshake, the client receives symbol, bid, and ask values as readable text.

It works from any language that can open a TCP socket. There is no proprietary runtime, SDK version, or platform-specific library to install on the client side.

The client can request an explicit symbol list when it connects. If no list is supplied, the connection can receive the full feed.

This protocol is commonly connected to a brokerage platform through the client’s existing bridge or integration layer. Connection and endpoint details are supplied during onboarding.

FIX 4.4 delivery

For downstream systems that already use FIX market data, CoinPriceFeeds supports FIX 4.4 delivery.

Two connection models are available:

• Acceptor mode: your system connects to CoinPriceFeeds and subscribes to the required symbols.
• Initiator mode: CoinPriceFeeds connects outbound to the endpoint you provide.

Subscription state is maintained per FIX session. One consumer can request a different symbol set from another, and a failure sending to one session does not stop delivery to the rest.

Specific message types and venue dialect requirements are confirmed during technical scoping.

Several consumers can share one pricing policy

The same client-specific feed can serve more than one platform integration. That avoids rebuilding the pricing calculation inside every destination.

Each consumer receives the output symbols it needs, while the sources, pricing rules, and protection remain central and consistent.

This is useful when a brokerage is:

• running more than one trading platform;
• migrating from one platform to another;
• separating client groups across environments;
• feeding an internal risk or reconciliation system alongside the trading platform; or
• keeping a primary and backup connection live at the same time.

Keepalive and configuration identity

The stream includes a lightweight keepalive so a client can distinguish a quiet market from a dead connection.

It also exposes a compact fingerprint of the pricing rules loaded on that server. A client or comparison tool can check that primary and backup endpoints are using the same configuration before a failover is needed.

The redundancy overview explains how that fingerprint is paired with live price and activity comparison.

Slow consumers do not block everyone else

A congested bridge or a slow network should not stall the pricing engine.

A slow consumer can receive a lower effective update rate while delivery continues to favor current prices over an unlimited backlog of old updates. Other consumers and the pricing engine continue independently.

Isolation by feed and connection

Each client feed has its own pricing state, output configuration, dashboard, and monitoring. FIX subscriptions are held per downstream session.

That keeps two important boundaries clear:

• an explicitly subscribed consumer receives only its requested symbols, while a streaming client may instead choose the full feed; and
• one client feed’s configuration or connection problem is contained to that feed as far as possible.

Tools for integration and diagnosis

CoinPriceFeeds can provide a small reference client that demonstrates the streaming handshake, subscription, parsing, and basic validation.

Additional diagnostic tools can:

• log the traffic in both directions during parser troubleshooting;
• compare primary and backup endpoints;
• check symbol liveness and spread agreement; and
• produce machine-readable results for an acceptance or release process.

The technology-team overview describes the path from endpoint details to production, while the feed evaluation guide lists useful questions to settle before integration begins.