Broker Connections

What Broker Connections is for

Broker Connections creates and verifies the provider accounts that a supported Live deployment can use. It keeps provider identity, environment, account selection, credentials, connection tests, and retained certification evidence together.

A configured connection is not permission to trade. Live still applies the deployment's mode, risk limits, readiness checks, operator actions, and current provider certification.

Create a connection

1. Select a provider currently offered by the workstation.
2. Choose the environment shown by that provider, such as a simulated or real-money environment where supported.
3. Enter a clear display name and any account identifier required at this stage.
4. Save the connection.
5. Store the provider-specific credential fields through the protected control.

Credential fields and authorization methods are provider-defined. A connection may use browser authorization, an application registration, a local gateway, key material, or another supported method. Follow the exact instructions shown for that provider rather than copying fields from a different integration.

Test and discover accounts

Use Test Connection to check the configured authentication path. A successful test establishes only what the displayed result says; it does not guarantee market-data entitlements, order permission, continuous connectivity, or Live certification.

When supported, Discover Accounts reads the accounts exposed by the current provider session. Select the exact account intended for the connection and verify its environment. Never infer Paper or real-money status from the account name alone.

Read readiness and certification separately

The page can show connection diagnostics, provider evidence, stream certification, calibration, and release-integrity state. These answer different questions:

• connection state — can Arizmic reach the configured provider session;
• account discovery — which accounts the provider exposes;
• stream evidence — which supported market or account streams have retained proof;
• calibration — whether current provider behavior fits the supported operating bounds; and
• release integrity — whether the running release matches the certified path.

Do not collapse these into one green light. The Live deployment page is the authority for whether a specific deployment can be armed.

Maintain or remove a connection

Edit the display name, account, or supported environment when the provider configuration changes, then retest and rediscover accounts. Removing a stored credential revokes Arizmic's protected secret reference but does not revoke it at the provider; use the provider's dashboard when the secret itself must be invalidated.

Remove an obsolete connection only after confirming no retained deployment depends on it. Historical Results and broker records remain separate from the connection configuration.

Provider availability is integration-, account-, and jurisdiction-specific. Consult the capability, provider, and broker matrix before planning a Live workflow.