Skip to main content
Programmatic equivalent of the dashboard’s resolver Settings page (resolver/settings/). It holds one value, the organization’s routing timezone.

When to use

  • A brand owner wants time-based rules (a weekend promotion, store hours, an annual season) to follow their local clock.
  • A brand owner wants to know which zone those rules are read in today.

What it does

A time-based rule (annual window, day of week, time of day) is read in the rule’s own timezone. A rule with no timezone of its own is read in the organization’s routing timezone; an organization with none stored uses UTC. Absolute start and end times are instants and do not depend on the zone. Changing this setting moves when every rule without its own timezone fires, so real consumers’ redirects change: tell your human first.

Auth

X-API-Key header or OAuth token with resolver:write scope (resolver:read for reads). Reading needs view access to the organization; writing needs an Owner or Manager and answers 403 for anyone else. The paths carry no organization: an API key acts on its own organization, and a session or OAuth caller on its only one. A caller in more than one adds ?organization_id=<id> (400 without it); naming an organization the caller cannot see answers 404.

Flow

  • Read — returns organization_id and routing_timezone.
  • Set — the body carries routing_timezone, an IANA name such as America/Chicago or Europe/Berlin.
  • Read back — the PUT returns the saved value; GET again to confirm.

Errors

403 for a caller who cannot write; 404 for an organization the caller cannot see; 422 for a timezone name that is not an IANA zone.

Notes

A rule’s own timezone always wins. To change one rule only, edit that rule (see manage-resolution-rules).