Dates and Time Zones

Use ISO 8601 timestamps and UTC for predictable filtering, scheduling, and time tracking.

Use ISO 8601 timestamps for all date and time values.

Recommended format:

2026-07-01T09:30:00Z

The Z suffix means UTC. Sending UTC timestamps is the safest option for integrations because it avoids ambiguity around local time zones and daylight saving changes.

Request Fields

Common timestamp fields include:

• createdAt
• updatedAt
• plannedStart
• plannedEnd
• scheduledStart
• scheduledEnd
• dueDate
• start
• end
• date
• time

Date Range Filters

Many list endpoints support From and To filters.

Examples:

GET /tasks?plannedStartFrom=2026-07-01T00:00:00Z
GET /tasks?plannedStartTo=2026-07-31T23:59:59Z
GET /times?startFrom=2026-07-01T00:00:00Z&startTo=2026-07-31T23:59:59Z
GET /scheduledWork?dateFrom=2026-07-01T00:00:00Z&dateTo=2026-07-31T23:59:59Z

See List tasks, List time entries, and List scheduled work for the full filter sets.

Time Tracking

When starting or stopping time tracking, send the event time explicitly:

{
  "userId": "USER_ID",
  "time": "2026-07-01T09:00:00Z"
}

This makes the integration deterministic and avoids relying on server receipt time.

Best Practices

• Store timestamps in UTC.
• Send timezone-aware timestamps.
• Avoid date-only values for fields that represent a precise moment.
• Convert to local time only in your user interface or reporting layer.