Availability
Controls are available on theProfessional plan tier.
Intended Purpose
Controls allow organizations to define restrictions that govern trading activity before orders are submitted to a broker. Anthid evaluates configured controls in real time and can prevent trading activity that violates organizational policies, risk limits, or trading schedules. Controls can be applied at multiple levels:- Organization Controls apply across an entire organization.
- Trading Account Controls apply to a specific trading account.
- Symbol Controls apply only to a specific symbol within a trading account.
Access
Most read operations use the caller’s principal organization. Service-account callers must providex-organization-id where supported, and the requested organization must own the trading account.
Create, update, and delete operations require Controls Premium and organization control edit access. Evaluation requires Controls Premium plus control read access for user and API-key callers, or the control:evaluate scope for service-account callers.
Control Hierarchy
Controls are evaluated at three levels. More specific controls apply to a narrower scope of trading activity.Control Types
Manual Controls
Manual controls provide a simple mechanism for enabling or disabling trading activity. Common use cases include:- Emergency trading halts
- Maintenance windows
- Compliance reviews
- Temporary account restrictions
Risk Controls
Risk controls enforce quantitative trading limits. Examples include:- Maximum daily loss amounts
- Maximum daily loss percentages
- Maximum position sizes
- Maximum order sizes
Time Controls
Time controls restrict when trading activity is permitted. Examples include:- Trading start times
- Trading end times
- Stale order thresholds
Endpoint Groups
Control Evaluation
When an order or trading action is evaluated, Anthid checks the effective organization, account, and symbol controls and determines whether the action should be permitted. If one or more controls are triggered, the evaluation response identifies:- The control scope
- The control type
- The reason the action was rejected
allowed boolean and a triggered list. Pass null to evaluate organization-level controls only, or pass an account id, symbol, and quantity to include account-level and symbol-level checks.
This allows applications to present meaningful feedback to users and operators.
Common Use Cases
- Disable trading during incidents or maintenance
- Restrict trading outside approved hours
- Enforce account-level risk limits
- Apply symbol-specific trading restrictions
- Implement organization-wide trading policies
- Build automated compliance workflows
Related Resources
- Trading Accounts
- Orders
- Positions
- Connections
- Control Evaluation