Date and Time Fields

To ensure that users are able to easily and consistently work with dates across all TeamDynamix applications, dates submitted through the Web API are handled using Coordinated Universal Time (UTC) standards.

Format

When submitting date and datetime fields through the Web API, values should match ISO 8601 standards. Values should generally match the following format:

YYYY-MM-DDThh:mm:ssTZD

The following table describes what part of the date and time is represented in the above datetime format string.

Component	Description
`YYYY`	Year
`MM`	Month
`DD`	Day
`T`	Separator between the date and time values.
`hh`	Hour
`mm`	Minute
`ss`	Second
`TZD`	Time offset

A time value can be offset from UTC using a time offset. This either follows the time value as the character Z (indicating UTC), or is set to the UTC offset in the format ±[hh]:[mm] or ±[hh][mm]. A full list of UTC offsets by time zone can be found here.

Times returned from the Web API will always be in UTC. When submitting new values for a datetime field, you may either use the UTC value or provide a UTC offset.

Date-Only Fields

Although full datetime values are accepted for all date and datetime fields, there are instances where only the date portion is used. For date-only fields, set the time component to 00:00:00 and include a time zone offset to prevent the date from shifting during storage, which can cause display problems across time zones.

Date-only values eturned from the server will have their time value set relative to the server it is being sent from. Care should be taken to ensure that these values are being treated properly when retrieving data through the Web API.

Date and Date/Time Custom Attributes

Custom Attributes configured as date or date/time fields follow the same formatting rules described above. For date-only Custom Attributes, standard date/time formatting works correctly, but you must still account for time zone offsets. To avoid this, date-only Custom Attributes also accept a simplified date-only format that omits the time and offset entirely. For example, 2026-03-15 will set the Custom Attribute to that date.

Examples

The following table shows how the same point in time (2026-03-15 14:30:00 UTC) can be expressed in several accepted formats.

Format	Date and Time Value	Date-Only Value
Coordinated Universal Time (UTC)	`2026-03-15T14:30:00Z`	`2026-03-15T00:00:00Z`
Eastern Standard Time (EST, UTC−5)	`2026-03-15T09:30:00-05:00` `2026-03-15T09:30:00-0500`	`2026-03-15T00:00:00-05:00` `2026-03-15T00:00:00-0500`
Eastern Daylight Time (EDT, UTC−4)	`2026-03-15T10:30:00-04:00` `2026-03-15T10:30:00-0400`	`2026-03-15T00:00:00-04:00` `2026-03-15T00:00:00-0400`
Pacific Standard Time (PST, UTC−8)	`2026-03-15T06:30:00-08:00` `2026-03-15T06:30:00-0800`	`2026-03-15T00:00:00-08:00` `2026-03-15T00:00:00-0800`