JSON endpoints for current weather and multi-day forecasts. No API key required for callers — geocoding and Google Weather requests run server-side.
https://atmofeed.com
Every endpoint accepts a required location query parameter. Use a city name, address, or comma-separated coordinates:
location=New Yorklocation=40.7128,-74.0060GET /api/weather?location=New York
Example:
curl "https://atmofeed.com/api/weather?location=London"
Response includes resolved place name, country code, coordinates, and a weather object with current conditions.
GET /api/forecast?location=New York&days=7
days is optional (1–10, default 7). The forecast starts from today.
Example:
curl "https://atmofeed.com/api/forecast?location=Tokyo&days=7"
{
"location": "London",
"resolvedLocation": "London, UK",
"countryCode": "gb",
"coordinates": { "latitude": 51.51, "longitude": -0.13 },
"weather": { ... }
}
Forecast responses use a forecast array instead of weather.
Production API routes are limited to 30 requests per minute per IP.
When exceeded, the API returns HTTP 429 with:
{ "error": "Too many requests" }
Responses include X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers.
Weather data comes from the
Google Weather API.
Some countries are not supported yet — for example Japan, China, and South Korea return no current conditions or forecast data.
Geocoding may still resolve the place name, but the weather endpoints respond with 404.
| Status | Meaning |
|---|---|
400 |
Missing or invalid location |
404 |
Location not found, or weather data unavailable for that place |
429 |
Rate limit exceeded |
503 |
Service unavailable |
Questions or issues? Email feedback@atmofeed.com.