Getting Started
Set up your account, check your network and receive your first prices.
Create your account
Sign up on hftfeed.com. The feed only accepts an email and a password, so remember the password you choose: you will use it in your application too.
If you signed up with Google, your account doesn't have a password yet. Open Settings → Profile → Authentication, click Connect with Password and choose one. It is added to the same account, so your plan and connection details stay as they are.
Choose a plan, or try it first
You need an active plan or a running trial to connect. Without one the Connection page shows no connection details and the server refuses your logon.
The 24-hour trial costs $50, paid in crypto, and is bought on the Trial page of your dashboard:
- It streams three symbols over FIX:
EURUSD (1013),GBPUSD (1016)andXAUUSD (2001). A subscription to any other key is refused with Insufficient Permissions; charts and history on the site are not restricted. - The 24 hours start at your first FIX logon, not when you pay. You have 48 hours after the payment confirms to make that first connection, so set your client up first.
- The $50 comes off your first plan if you subscribe within 7 days of the trial ending. The checkout applies it automatically; it does not combine with a discount code.
- One trial per account. Trials are not refundable. There is no free trial.
The plan carries every symbol on the feed. Compare the plans on the pricing page and manage yours on the Subscriptions page. Plans are paid in crypto, for a fixed period; nothing renews by itself. Buying a plan while a trial is running simply replaces the trial: your session reconnects once and every symbol is available, on the same connection settings.
Find your connection details
Open Connection in your dashboard. The Fix Server card shows everything you need:
- Quote Login: your email, used as the FIX Username.
- Quote Password: your hftfeed.com password (not displayed).
- Quote Sender Comp ID: your SenderCompID.
- Quote Target ID:
FixServer. - Quote Host and Quote Port:
fix-server.hftfeed.comand9030. - Sender Sub Id and Target Sub Id:
QUOTE.
The .NET SDK looks up your SenderCompID for you, so there you only need the email and password.
Check your network
Your machine must be able to resolve fix-server.hftfeed.com and open outbound TCP connections to it on port 9030. If
your network blocks that port, use 9031 instead: it serves the same feed. The .NET SDK also needs outbound HTTPS
(port 443) to identitytoolkit.googleapis.com to sign you in.
Allow the host name in your firewall rather than an address. The name is what every client, the docs and the Connection page use, and the address behind it can change.
To test the port on macOS or Linux:
nc -vz fix-server.hftfeed.com 9030
On Windows (PowerShell):
Test-NetConnection fix-server.hftfeed.com -Port 9030
Both commands connect and disconnect straight away. Don't leave a raw connection open without logging on: the server closes it after 5 seconds, and repeated occurrences, or more than 6 connections per minute, temporarily block your IP address.
Connect
You subscribe with a symbol's numeric key (tag 55), not its name: 1013, not EURUSD. The
symbol coverage page lists every symbol with its key, and the client downloads the same
list on every logon.
- .NET 8 or later: follow the quick start in Connect with the .NET SDK. You will see live prices in a few minutes.
- Any other language or FIX engine: follow the FIX protocol reference.
Rules to keep in mind
- One live session per account, across both ports. Log out before you connect again.
- Up to 64 subscriptions per session and up to 50 messages per second from your side.
- Read continuously. If your application falls behind for 10 seconds, the server ends the session.
- Plain TCP. The connection is not encrypted, so use a password you don't use anywhere else.
- Don't retry failed logons in a loop. Repeated failures temporarily block your account and IP address.
The full list is in the limits section.
Need help?
Contact us through support. Include your SenderCompID, the time of the problem (UTC) and any error text you received. Never send your password.