Time value formats
- Last UpdatedApr 16, 2026
- 3 minute read
CONNECT supports the following primary time value formats in different services:
ISO 8601 datetime format
Use this format to specify exact timestamps for absolute time boundaries across CONNECT services. Use it when retrieving data for a specific date, time, or time range.
Applies to services
|
Service |
Applies |
Notes |
|---|---|---|
|
Stream Store (SDS) |
Yes |
Used for startIndex and endIndex on datetime-indexed streams. |
|
Data View Management |
Yes |
Used for startIndex and endIndex when the data view has a DateTime or DateTimeOffset index. |
|
Virtual Table Management |
Yes |
Used for materialization materializationStart and materializationEnd. |
|
Event Management |
Yes |
Used for event startTime and endTime, and for query window filters such as startsAfter and startsBefore. |
Format
YYYY-MM-DDThh:mm:ssZ
Use this as the recommended interoperable datetime format in CONNECT documentation and request examples. For Data View Management, datetime index values are parsed using .NET date parsing with round-trip semantics, so equivalent ISO 8601-compatible values may also be accepted. In examples, prefer full UTC timestamps with the Z suffix because they are the clearest and most portable form across services.
Components
-
YYYY: Four-digit year
-
MM: Two-digit month (01-12)
-
DD: Two-digit day (01-31)
-
;T: Literal separator between date and time
-
hh: Two-digit hour (00-23)
-
mm: Two-digit minute (00-59)
-
ss: Two-digit second (00-59)
-
Z: Literal indicator for UTC timezone
Examples
These are practical datetime values you can use in CONNECT API requests. In examples, include the full date, time, and UTC indicator to avoid ambiguity. Modify the date and time values according to your specific query needs.
-
2024-01-15T00:00:00Z: Start of January 15, 2024 (UTC)
-
2024-12-31T23:59:59Z: End of December 31, 2024 (UTC)
-
2024-06-15T14:30:00Z: June 15, 2024 at 2:30 PM (UTC)
Common use cases
These are the most frequent scenarios where absolute timestamps are needed across CONNECT services:
-
Virtual table materialization start/end times
-
Stream data query time ranges
-
Data view historical data queries
-
Job filtering by timestamp
ISO 8601 duration format
Use this format for Virtual Table Management job history duration filtering.
Applies to services
|
Service |
Applies |
Notes |
|---|---|---|
|
Stream Store (SDS) |
No |
SDS interpolation commonly uses count rather than a duration filter expression. |
|
Data View Management |
No |
Data view interpolation interval parameters use .NET TimeSpan strings. |
|
Virtual Table Management |
Yes |
Job history duration filter uses ISO 8601 duration with a comparison operator (for example, PT1H30M GT). |
|
Event Management |
No |
Event request and query parameters use ISO 8601 datetime values rather than ISO 8601 duration filters. |
Format
duration=<ISO 8601 duration> <operator>
Use ISO 8601 duration values such as PT1H30M and combine them with a duration comparison operator used by the endpoint.
ISO 8601 duration reference
-
PT45S: 45 seconds
-
PT5M: 5 minutes
-
PT30M: 30 minutes
-
PT1H: 1 hour
-
PT1H30M: 1 hour and 30 minutes
-
P1D: 1 day
-
P2DT12H: 2 days and 12 hours
Valid duration comparison operators
-
LT: Less than
-
LTE: Less than or equal to
-
GT: Greater than
-
GTE: Greater than or equal to
Examples
-
PT1H30M GT: Greater than 1 hour and 30 minutes
-
PT45S LTE: Less than or equal to 45 seconds
.NET TimeSpan format
Use this format for Data View Management interval parameters and Virtual Table Management interval fields.
Applies to services
|
Service |
Applies |
Notes |
|---|---|---|
|
Stream Store (SDS) |
No |
SDS interpolation commonly uses count instead of an interval string. |
|
Data View Management |
Yes |
Interpolated data interval values are parsed as .NET TimeSpan strings. |
|
Virtual Table Management |
Yes |
Interval fields, including refreshInterval, are validated as .NET TimeSpan strings (for example, 01:00:00 or 1.00:00:00). |
|
Event Management |
No (request input) |
Event responses include computed duration values as date-span/TimeSpan-like strings, but request time fields use ISO 8601 datetime values. |
Format
[d.]hh:mm:ss
Use hh:mm:ss for hours, minutes, and seconds. Include d. when the duration spans one or more days. Data View Management parses valid .NET TimeSpan strings, so this pattern is the clearest format to document and use in examples, not the only form the parser may accept.
Examples
-
01:00:00: One hour
-
00:30:00: Thirty minutes
-
1.00:00:00: One day (day component is optional)
-
2.12:00:00: Two days and twelve hours