Set it up
- Issue the login at the provider with the market-data entitlements your traders should have. It’s the same decision you already make there.
- Pre-register the account so the trader finds it waiting in Connect when they sign in.
Know what trdrs does with the login
- One data connection per trader. trdrs builds it from the trader’s own stored login. A trader with accounts at several venues streams from one of their logins, and if that login is disconnected, the next request rebuilds from a login that remains.
- Bars and quotes kept apart. Bars and history use one connection and live quotes use a second, so a login without a quote entitlement still charts bars.
- The provider’s session rules hold. Where a provider allows one live session per login, the application that signs in last takes the session. trdrs reconnects once, and if the session is taken again it stops rather than fight the other application for it. Each provider’s entry on Providers states its own rule.
Choose a published feed instead
Provider data covers markets your traders already reach through their provider login. For data trdrs doesn’t connect to, such as your venue’s own index or a market trdrs doesn’t carry, run a small HTTP feed and register it with trdrs: Publish a datafeed. Start with provider data and reach for a published feed second. A published feed is a server your venue keeps running, while provider data rides on a decision you already make at your provider.Next steps
Register an account
Pre-register a trader so their account and its data are waiting at sign-in.
Publish a datafeed
Serve your traders data from a market trdrs doesn’t connect to.