Guide

DST and business-day calculations API

Daylight-saving changes and business-day logic are where time APIs stop being trivial utilities.

DST changes affect more than display

DST transitions change offsets, calendar boundaries, and user-facing expectations. A serious API should expose both current status and transition-related context instead of leaving every app to infer it indirectly.

Business-day math belongs near the time engine

Elapsed-time and diff workflows become much more useful when they can count weekdays or holiday-aware business days. That lets teams keep operational scheduling logic in one place instead of stitching together separate calendar services.

Related endpoints

Daylight-saving status for a target

Use DST status when offset change awareness matters to scheduling, billing windows, or user-facing time displays.

Open endpoint

Time elapsed since or remaining until a reference instant

Use elapsed when you need time since or time until a reference instant, optionally relative to another explicit comparison instant.

Open endpoint

Difference between two instants

Use diff when you need the distance between two explicit instants rather than a relative now-to-target calculation.

Open endpoint