Data Format Requirements
Time Series Structure
Your time series data must follow this JSON structure:Timestamp Format
ISO 8601 Format
ISO 8601 Format
All timestamps must be in ISO 8601 format:
YYYY-MM-DDTHH:MM:SSExamples:2023-01-01T00:00:00(Daily data)2023-01-01T10:30:00(Hourly data)2023-01-01T10:30:45(Minute-level data)
Use consistent timezone formatting. We recommend UTC for global applications.
Supported Frequencies
Supported Frequencies
The API supports these data frequencies:
- Seconds: High-frequency data (e.g., stock prices, sensor readings)
- Minutes: Sub-hourly data (e.g., website traffic, IoT metrics)
- Hours: Hourly data (e.g., energy consumption, temperature)
- Daily: Daily data (e.g., sales, website visits)
- Weekly: Weekly aggregations (e.g., weekly revenue, user growth)
- Monthly: Monthly data (e.g., monthly sales, subscription metrics)
- Quarterly: Quarterly data (e.g., quarterly earnings, seasonal trends)
- Yearly: Annual data (e.g., yearly revenue, long-term trends)
Data Quality Requirements
Minimum Data Points
Daily/Weekly: At least 30 data points
Monthly/Quarterly: At least 12 data points
Yearly: At least 5 data points
Hourly/Minutes/Seconds: At least 100 data points
Monthly/Quarterly: At least 12 data points
Yearly: At least 5 data points
Hourly/Minutes/Seconds: At least 100 data points
Data Completeness
No missing values in timestamps or values arrays
Arrays must have equal length
Values must be numeric (integers or floats)
Timestamps must be in chronological order
Arrays must have equal length
Values must be numeric (integers or floats)
Timestamps must be in chronological order
Data Preparation Best Practices
1. Data Cleaning
Handle Missing Values
Handle Missing Values
Before sending data to the API, ensure you’ve handled missing values:
Outlier Detection
Outlier Detection
Consider removing or smoothing extreme outliers that could skew forecasts:
2. Seasonality Considerations
Daily Seasonality
For daily data, consider day-of-week patterns. Include at least 4 weeks of data to capture weekly seasonality.
Monthly Seasonality
For monthly data, include at least 2 years of data to capture annual seasonality patterns.
3. Data Granularity
Choose the right frequency: Use the highest frequency that makes sense for your use case. Higher frequency data can capture more patterns but requires more data points.
Setup Considerations
API Configuration
Model Selection
Model Selection
Choose the appropriate model based on your data characteristics:
- forecast-model-1: General purpose, good for most use cases
- forecast-model-2: Better for complex seasonal patterns
- forecast-model-3: Optimized for high-frequency data
- forecast-model-4: Advanced deep learning for complex patterns
Forecast Horizon
Forecast Horizon
Set your forecast horizon based on your business needs:
- Short-term: 1-7 periods for immediate planning
- Medium-term: 8-30 periods for operational planning
- Long-term: 30+ periods for strategic planning
Longer forecast horizons generally have higher uncertainty. Consider using confidence intervals for planning.
Common Data Patterns
Example: E-commerce Sales Data
Example: Website Traffic (Hourly)
Troubleshooting
Common Errors
Common Errors
“Invalid timestamp format”: Ensure timestamps are in ISO 8601 format
“Arrays must have equal length”: Check that timestamps and values arrays have the same number of elements
“Insufficient data points”: Add more historical data points
“Invalid frequency”: Use one of the supported frequency values
“Arrays must have equal length”: Check that timestamps and values arrays have the same number of elements
“Insufficient data points”: Add more historical data points
“Invalid frequency”: Use one of the supported frequency values
Performance Tips
Performance Tips
- Use consistent time intervals when possible
- Pre-process data to remove noise and outliers
- Consider data seasonality when choosing forecast horizon
- Test with smaller datasets before processing large volumes

