Holiday Handling

This guide covers time-sensitive operations and emergency procedures that Prop Trading Firms need to handle when integrating with the Tradovate Partner API. These procedures help you manage critical timing windows and emergency situations effectively.

Quick Reference

End-of-Month Market Data Subscription Process

Critical Timing Windows

When calling addMarketDataSubscription or manually adding market data through the Dashboards on the last day of the month, it is important to ensure that data is added for the correct month.

Before 7:00 PM CT

• Market data for the current month should be added
• All subscription operations should target the ending month

After 7:00 PM CT

• Any market data that is added should be for the upcoming month
• Avoid adding data for the ending month during this window

Renewal Window

The market data renewal window runs from 7:00 PM CT until 4:00 AM CT the following morning, with the majority of renewals taking place between 7:00 PM and 8:00 PM CT.

Emergency Trading Halt Procedures

Individual Account Halts

• Halted-trading category: Can be applied to individual accounts
• Risk Category changes: Used to halt trading for specific accounts
• Account state management: Return accounts to SOD (Start of Day) state

Category-Wide Halts

• Emergency halt: Halt trading for an entire category
• Use case: Stop all, or specific categories of users from trading in an emergency
• Implementation: Change Risk Category for entire user groups

Account State Management

• SOD state: Return an account to its Start of Day state at a given date
• Session date vs Calendar date: Use session date, not calendar date for state management
• Emergency recovery: Restore accounts to known good states

Time-Sensitive API Operations

Account Creation

• Avoid calling account creation endpoints during maintenance windows
• Queue requests and submit them after maintenance windows conclude
• Add 15–30 minute buffer before and after maintenance windows

Subscription Management

• Handle subscription renewals during end-of-month windows
• Monitor renewal status and handle failures appropriately
• Implement retry logic for time-sensitive operations

Risk Management

• Monitor account risk status in real-time
• Implement emergency halt procedures
• Handle risk category changes during critical periods

Best Practices

Time Zone Handling

• All times are in Central Time (CT)
• Implement proper time zone conversion in your applications
• Account for daylight saving time changes

Monitoring and Alerts

• Set up monitoring for end-of-month processes
• Implement alerts for emergency situations
• Monitor subscription renewal status

Error Handling

• Implement robust error handling for time-sensitive operations
• Use retry logic with exponential backoff
• Log all time-sensitive operations for audit purposes

Emergency Procedures

• Document emergency halt procedures
• Train staff on emergency response protocols
• Test emergency procedures regularly

Implementation Guidelines

API Integration

• Use WebSocket connections for real-time monitoring
• Implement proper heartbeat mechanisms
• Handle connection failures gracefully

Data Management

• Store time-sensitive configuration data securely
• Implement proper backup and recovery procedures
• Monitor data integrity during critical periods

Compliance

• Ensure all time-sensitive operations are logged
• Implement proper audit trails
• Follow regulatory requirements for emergency procedures