Customer applications interact with MarketFactory API through the adoption of Whisperer users. These user details provide the credentials for the establishment of connectivity to the platform and the creation of sessions, that can accept requests
Historically usernames such as "ProdUser1" had sometimes been used in Whisperer configurations. These are limiting for several reasons, not least of which is the fact that they are not globally unique across different Whisperer instances (where a customer has more than one instance of Whisperer).
Usernames should follow the format mnemonic-environment-purpose-instance, where mnemonic is the three/four-letter identifier for a customer, the environment is one of UAT, or PROD, the purpose is one of trading, dropcopy, admin, api, and the instance is a three-digit identifier. While this format appears lengthy, it aims to strike a balance between brevity and clarity.
Whisperer system users have different roles, so a component of the username should indicate this. Here are some examples:
example username | purpose name | description |
|---|---|---|
bwp-prod-trading-001 | trading | regular trading users, used for market data and order entry |
bwp-prod-data-001 | data | used for market data only, does not have trading rights |
bwp-prod-dropcopy-001 | dropcopy | dropcopy subscriptions, does not have trading rights |
bwp-prod-admin-001 | admin | administrative users, for NOP setting |
bwp-prod-mm-001 | mm | market-making trading |
bwp-prod-api-001 | api | regular usage via the API |