What a trader is
A trader is a member of your organization added with the trader role. The trading platform is the only surface they have.
See Organization for roles and what an admin does.
Adding a trader
An admin adds a trader in two steps, both in the Platform:
- Add them to the organization as a trader. They can then sign in to the trading platform.
- Add them to each pod they should trade.
Access is per pod: a trader with no pod can sign in but cannot trade, and removing one pod leaves the others.
What a trader can do
Two settings an admin controls decide what a trader can do:
API keys
A trader who may create keys creates them from the trading platform, one key per pod. The keypair is generated in their browser: ParlayX registers the public half and never sees the private one, which the trader is shown once.
Each key carries one permission, set by your organization: some organizations issue data keys only, others issue data and trade.
A trade key is for a trader placing orders. It can:
- Place orders in its pod
- Read its own orders and fills
- Cancel its own orders
- Read its pod’s balance and positions
- Read market data: discovery and the orderbook stream
A data key is for a consumer that never trades, such as a data or monitoring
integration. It can:
- Discover markets and look one up
- Subscribe to the orderbook stream
See Authentication for the full capability table and how a request is verified.
Attribution
Every order carries the trader that placed it. That gives you, without any additional work:
- Per-trader position, derived from that trader’s own fills
- Per-trader realized and unrealized P&L
- A complete record of who did what, in which pod, at which venue
See Portfolio and positions.
Rotate, revoke, remove
Removing a trader does not close their positions. Those positions remain open, and remain the pod’s. Manage them from the Platform or through another trader in the pod.
