Two Minute Reports Logo
Teams

Update team timezone

Set the IANA zone a team works in.
PUT /teams/{teamId}/timezone

Sets the timezone the team works in. One zone per team.

Authentication: Bearer token · Permission:teams:write · Team permission:team_settings.write · Rate limit: default (120 / 60s)

What the timezone drives

  • The daily schedule-failure summary. One email per team per morning, listing the scheduled queries that failed the previous day. It is sent on this zone, so this is the setting that decides whether it lands at breakfast or overnight.
  • The query log sheet. Timestamps written to a team's log sheet are formatted in this zone.
  • Query defaults that follow the team. A team whose default timezone — or whose provider-timezone fallback — is set to follow the team inherits this value.
It does not change when a schedule runs. Schedules carry their own timezone and are untouched by this setting. Changing it moves when we mail the team, not when their reports execute.

Path parameters

teamId
string · uuid v7 required
The ID of the team whose timezone is being set.

Request body

timezone
string | null required
An IANA zone name such as Asia/Kolkata or America/New_York. Abbreviations and UTC offsets (IST, GMT+5:30) are rejected. Send null to clear it, which resolves back to UTC.
{ "timezone": "Asia/Kolkata" }
Setting a zone through the API marks it as chosen by a person, the same as setting it in the app. A team that has never had one set adopts the zone of the first browser that reports one; once this endpoint has written a value, that automatic adoption stops for the team. Clearing it with null hands the team back to that automatic behaviour.

Request

curl -X PUT https://api.twominutereports.com/v1/teams/0190f8b0-1a2b-7c3d-8e4f-5a6b7c8d9e0f/timezone \
  -H "Authorization: Bearer tmrc_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"timezone": "Asia/Kolkata"}'

Response

{
  "success": true,
  "data": { "timezone": "Asia/Kolkata" }
}
Copyright © 2026