Clock change API
Free JSON files with the next UK clock changes. No sign-up or API key needed.
Endpoints
- GET https://whendotheclockschange.uk/api/v2.json Recommended
- GET https://whendotheclockschange.uk/api/latest.json Newest version (currently v2)
- GET https://whendotheclockschange.uk/api/v1.json Legacy
- GET https://whendotheclockschange.uk/calendar.ics Calendar feed (iCalendar)
Use v2.json for anything new. It has both upcoming changes, the exact time of each in UTC and UK time, the GMT/BST offsets either side, and whether the UK is on summer time right now. It has no display text, so you can word things however you like.
The calendar feed has an all-day event for each change from last year to 10 years ahead. You can subscribe to it in any calendar app.
Credit
The API and calendar feed are free to use. If you use them in something public, please link back to this site. It helps other people find accurate clock change dates. You can copy this:
Clock change dates from <a href="https://whendotheclockschange.uk/">When do the clocks change?</a>
Example response (v2)
This is the current response from /api/v2.json.
{
"api_version": "2.0",
"generated_at": "2026-11-20T19:53:43Z",
"timezone": "Europe/London",
"current_offset": "+00:00",
"current_timezone_name": "GMT",
"in_daylight_saving": false,
"next_change": {
"date": "2027-03-28",
"datetime_utc": "2027-03-28T01:00:00Z",
"datetime_local": "2027-03-28T01:00:00+00:00",
"type": "spring_forward",
"days_until": 128,
"offset_before": "+00:00",
"offset_after": "+01:00",
"timezone_name_before": "GMT",
"timezone_name_after": "BST",
"hour_change": 1
},
"upcoming_changes": [
{
"date": "2027-03-28",
"datetime_utc": "2027-03-28T01:00:00Z",
"datetime_local": "2027-03-28T01:00:00+00:00",
"type": "spring_forward",
"days_until": 128,
"offset_before": "+00:00",
"offset_after": "+01:00",
"timezone_name_before": "GMT",
"timezone_name_after": "BST",
"hour_change": 1
},
{
"date": "2027-10-31",
"datetime_utc": "2027-10-31T01:00:00Z",
"datetime_local": "2027-10-31T02:00:00+01:00",
"type": "autumn_back",
"days_until": 345,
"offset_before": "+01:00",
"offset_after": "+00:00",
"timezone_name_before": "BST",
"timezone_name_after": "GMT",
"hour_change": -1
}
]
}
Response fields (v2)
| Field | Description |
|---|---|
api_version | API version number ("2.0") |
generated_at | ISO 8601 timestamp (UTC) when the data was generated |
timezone | IANA timezone identifier ("Europe/London") |
current_offset | Current UTC offset ("+00:00" or "+01:00") |
current_timezone_name | Current timezone abbreviation ("GMT" or "BST") |
in_daylight_saving | Whether the UK is currently on British Summer Time |
next_change | The next clock change (same shape as the items below) |
upcoming_changes | Array of both upcoming changes, spring first, each with: |
date | ISO 8601 date (YYYY-MM-DD) |
datetime_utc | When the change happens, in UTC |
datetime_local | When the change happens, in UK local time with offset |
type | "spring_forward" or "autumn_back" |
days_until | Number of days until this change |
offset_before / offset_after | UTC offset before and after the change |
timezone_name_before / timezone_name_after | "GMT" or "BST" |
hour_change | Clock adjustment: 1 forward, -1 back |
Usage examples
Pythonimport requests
data = requests.get("https://whendotheclockschange.uk/api/v2.json").json()
print(f"Currently on {data['current_timezone_name']}")
print(f"Next change: {data['next_change']['type']} on {data['next_change']['date']}")
print(f"Days until: {data['next_change']['days_until']}")
for change in data["upcoming_changes"]:
print(f"{change['type']}: {change['date']} ({change['days_until']} days)")
JavaScript
const response = await fetch('https://whendotheclockschange.uk/api/v2.json');
const data = await response.json();
console.log(`Currently: ${data.current_timezone_name} (${data.current_offset})`);
console.log(`Next change: ${data.next_change.type} in ${data.next_change.days_until} days`);
for (const change of data.upcoming_changes) {
console.log(`${change.type}: ${change.date}`);
}
curl
curl https://whendotheclockschange.uk/api/v2.json
Migrating from v1 to v2
| v1 field | v2 equivalent | Notes |
|---|---|---|
version | api_version | Renamed for clarity |
data.date | next_change.datetime_utc | Now includes the actual time of the change, with timezone |
data.type | next_change.type | "forward" → "spring_forward", "back" → "autumn_back" |
data.days_until | next_change.days_until | Unchanged |
data.change | Removed | Build your own text from the structured data |
| n/a | upcoming_changes | New: both spring and autumn changes |
| n/a | current_offset, in_daylight_saving | New: current timezone status |
API v1 (legacy)
Kept for backward compatibility. New integrations should use v2.
{
"version": "1.0",
"generated_at": "2026-11-20T19:53:43.897975",
"data": {
"date": "2027-03-28T00:00:00",
"type": "forward",
"days_until": 128,
"change": "At 1:00am, clocks go forward to 2:00am"
}
}
Notes
- The files are rebuilt several times a day, including just after midnight UK time, so
days_untilis current. - Dates and times are ISO 8601.
days_untilcounts calendar days in UK time. - No authentication required. Served over HTTPS with CORS enabled, so you can call it from the browser.
- Please cache responses: the data only changes twice a day.
- Use a versioned endpoint (
v1.json,v2.json) for stability.latest.jsoncurrently matches v2 and may change in future. - v1 will remain available for backward compatibility.