Visual Crossing Weather API
Legacy Weather API removal
Stops workingSubscribe to Visual Crossing Weather APIShare
On December 31, 2026, the Legacy Weather API will be retired. This change affects calls to /VisualCrossingWebServices/rest/services/weatherdata/*. After that day, requests sent to these endpoints will fail.
Calls it hits
/VisualCrossingWebServices/rest/services/weatherdata/*
What to use instead of these calls
Call the Timeline Weather API instead using GET /VisualCrossingWebServices/rest/services/timeline/{location}/{date1}/{date2} for forecast, history, and summaries from one endpoint.
In Visual Crossing Weather API's words
The Legacy Weather API is scheduled to be retired on December 31, 2026
Facts
- API
- Visual Crossing Weather API
weather.visualcrossing.com - Kind
- Removal
- Announced
- March 2, 2026
- Takes effect
- December 31, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Visual Crossing Weather API's own pages
Questions
When does this change take effect?
Calls to /VisualCrossingWebServices/rest/services/weatherdata/* on Visual Crossing Weather API stop working on December 31, 2026.
What happens to calls after December 31, 2026?
They fail from that day.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix before December 31, 2026.