Skip to main content

Dates and times

Timestamps in responses​

Every timestamp FieldTask returns is in UTC with a Z suffix, for example 2026-11-10T14:00:00Z or 2026-11-03T14:05:12.481Z. The number of fractional digits varies, so parse timestamps rather than comparing them as strings.

Timestamps you send​

When an input takes a timestamp, such as a job's starts_at and ends_at:

  • Send a full timestamp with seconds and an explicit offset: 2026-11-10T09:00:00-05:00 or 2026-11-10T14:00:00Z.
  • Timestamps without an offset are rejected, and so is the offset -00:00.
  • Up to six fractional-second digits are accepted.
  • Time-zone names such as America/New_York aren't accepted. Convert to the offset in effect on that date at the job site, including any daylight-saving change.

FieldTask stores the instant you send. 09:00:00-05:00 comes back as 14:00:00Z.

Calendar dates​

Some inputs and filters are calendar dates (YYYY-MM-DD) rather than instants, such as scheduled_date on List jobs. These are interpreted in your organization's time zone, set in FieldTask. When the server resolves a date for you, for example scheduled_date=today, the response shows the date and time zone it used.

Each endpoint states which time zone its date fields use.