Developers
Dates and time zones
The API returns three kinds of time value. Each is read the way the Production Engine app itself reads it, so the API and the app always show the same day.
Three kinds
| Kind | Format | Fields |
|---|---|---|
| Shoot-day date, in the workspace time zone | YYYY-MM-DD | a shoot day's date |
| Calendar date, as entered | YYYY-MM-DD | a project's start_date and end_date, a deliverable's due_date |
| Instant, in UTC | 2026-10-01T15:00:00.000Z | every created_at, updated_at and other _at field |
The workspace time zone
GET /me returns the workspace's zone as workspace.time_zone, an IANA name such as America/Los_Angeles. Every shoot day also carries it as time_zone. A workspace that has not chosen a zone uses UTC.
A shoot day's date is the day in that zone, and its call_time and wrap_time are clock times there, exactly as the producer typed them (usually HH:MM).
Calendar dates
Project start and end dates and deliverable due dates are the dates the producer picked. They carry no time zone: read them as plain calendar dates, and do not convert them.
Parse a YYYY-MM-DD value as a date, not as midnight UTC, or a client west of UTC will show the day before.