Time syntax for CONNECT services

CONNECT API services support multiple time syntax formats for specifying time values, time ranges, and time intervals for supported services. Understanding these formats is essential for querying timeseries data, retrieving data views, managing virtual tables, and creating or querying events through REST API requests.

This page provides a comprehensive API reference for time syntax formats used in CONNECT, including practical request examples for each format. This topic applies to API contracts and payloads, not UI date/time display or entry behavior.

How to use these topics

• Start with Time syntax quick reference to identify which format your service expects.

• Use the matching format details to validate syntax and required components.

• Go to Time syntax use cases by service for copy-ready request paths and request bodies.

• Validate request paths and parameter contracts against each service's current public API specification before implementation.

Services using time syntax

CONNECT includes several services that work with time-based data. Each service has different time syntax requirements based on its purpose and use cases. This list highlights the services where time syntax is used most often. Other CONNECT services may also use time syntax in specific endpoints or scenarios.

• Stream Management: Low-level timeseries data storage and retrieval with flexible index types.

• Data View Management: Automated views of aggregated stream data with explicit type awareness.

• Virtual Table Management: Materialization of data views to external storage with explicit materialization windows and refresh schedules.

• Event Management: Event creation and query workflows that use explicit datetime fields and time-window filters.