Skip to content
Endpoint guide

DST status

GET /v1/time/dstOpenAPI YAML

Whether a zone is currently observing daylight saving time, plus the resolved local time.

What do I need to send?

Required / choose this first

A target selector is optional; omit it for UTC or choose one of tz, ip, lat + lon, or offset.

Optional

next includes the next transition when available. format and sign are optional.

Rule: Fixed offsets always return dst_active=false because they have no DST rules.

NameNeeded?Use it for
tzChoose one targetIANA timezone.
ipChoose one targetIPv4 or IPv6 address.
latPair parameterLatitude, pair with lon.
lonPair parameterLongitude.
offsetChoose one targetFixed UTC offset (URL-encode + as %2B). Always returns dst_active=false.
auto_tzChoose one targetSet true to use the request IP's timezone.
formatOptionalstrftime pattern for an additional `formatted` field, e.g. %Y-%m-%d %H:%M:%S.
nextOptionalSet true to include next_transition: the next UTC offset change, or null if none is scheduled.
signOptionalSet true for a signed response.

Code samples

Copy a request in your preferred language and replace YOUR_TIMELOGIC_API_KEY with your direct API key.

curl "https://api.timelogicapi.com/v1/time/dst?tz=Europe/Paris" \
  -H "Authorization: Bearer $TIMELOGIC_API_KEY"

Example response

{
  "unix": 1778093027,
  "unix_ms": 1778093027004,
  "utc": "2026-05-06T18:43:47Z",
  "iso_local": "2026-05-06T20:43:47+02:00",
  "rfc2822": "Wed, 06 May 2026 20:43:47 +0200",
  "human": "May 6, 2026, 8:43 PM Europe/Paris",
  "day_number": 4,
  "day_short": "Wed",
  "day_full": "Wednesday",
  "timezone": "Europe/Paris",
  "dst_active": true
}
Additional endpoint notes
https://api.timelogicapi.com/v1/time/dst?tz=Europe/Paris
https://api.timelogicapi.com/v1/time/dst?ip=8.8.8.8

Use at most one selector family. If no selector is provided, the response is for UTC (iso_local and timezone are null).

Always "now". This endpoint reports DST for the current request time only. It takes no timestamp input, and unix, unix_ms or iso are ignored if sent. To ask whether DST was active at another moment, call /v1/time/convert for that instant and compare its offset with the zone's standard offset.

next_transition. With next=true the response adds next_transition:

{
  "timezone": "America/New_York",
  "dst_active": true,
  "next_transition": "2026-11-01T02:00:00-04:00"
}
  • It is a string: the instant of the next UTC offset change, written in the offset that applies before the change. The new offset is not returned; call convert just after the transition if you need it.
  • It is null when no future offset change is scheduled (for example Asia/Tokyo), for offset targets, and when no selector is given.
  • The key is absent unless next=true.
  • It tracks UTC offset changes only. A zone can change dst_active without an offset change: under tzdata 2026e, America/Vancouver moves from PDT (DST) to permanent MST at the same −07:00 on November 1, 2026, so dst_active becomes false with no next_transition reported.
  • dst_active follows tzdata, including negative DST: Europe/Dublin reports true in winter.

When to use this endpoint

Use DST status to determine whether a resolved target is currently observing daylight saving time. It is best for timezone diagnostics, support tooling, calendar UI warnings, and systems that need to explain offset changes.

Request model

Choose at most one selector family: tz, ip, lat + lon, offset, or auto_tz=true. If no selector is provided, the response defaults to UTC. Fixed offsets are not zones and therefore always return dst_active=false because a numeric offset has no daylight-saving rules.

Display guidance

Pair dst_active with timezone, iso_local, and utc when showing users why local time differs from a standard offset. This is especially helpful around spring-forward and fall-back transitions.

Frequently asked questions

How do I check if daylight saving time is active?

Call GET /v1/time/dst?tz=Europe/Paris. dst_active is true while the zone observes DST, following tzdata.

How do I get the next DST change?

Add next=true. next_transition is the instant of the next UTC offset change, written in the offset that applies before the change, or null when none is scheduled.

Can I ask about DST at another date?

This endpoint always reports the current request time. For another moment, call /v1/time/convert for that instant and compare its offset with the zone's standard offset.