canonical: https://jentic.com/apis/accuweather.com/accuweather # AccuWeather API Jentic publishes the only available OpenAPI specification for AccuWeather API, keeping it validated and agent-ready. AccuWeather provides current conditions, daily and hourly forecasts, severe weather alerts, and lifestyle indices for any location worldwide. The API resolves locations through a city search or geoposition, returns a location key, and then serves weather data keyed off that location key. Authentication is via an apikey query parameter, and the base URL is dataservice.accuweather.com. ## For AI agents Look up a location and retrieve current conditions, 5-day daily forecasts, 12-hour hourly forecasts, alerts, and lifestyle indices from AccuWeather so agents can answer weather questions for any global location. ## Scope Does not handle weather radar tiles, historical weather archives, or air quality measurements - use for current conditions, daily/hourly forecasts, alerts, and indices on AccuWeather only. ## Capabilities - Resolve a city name into an AccuWeather locationKey via /locations/v1/cities/search - Resolve latitude and longitude into a locationKey via /locations/v1/geoposition/search - Retrieve current weather conditions for a locationKey - Retrieve a 5-day daily forecast for a locationKey - Retrieve a 12-hour hourly forecast for a locationKey - Pull active severe weather alerts for a locationKey - Retrieve daily lifestyle indices (running, allergy, beach, etc.) for a locationKey ## Use cases ### Travel App Weather Cards A travel itinerary app shows a weather card for each destination by first calling /locations/v1/cities/search to resolve the city name, then /forecasts/v1/daily/5day/{locationKey} for the trip dates. Travelers see expected conditions before they pack. Caching the locationKey per destination reduces repeat resolution calls. Example prompt: Resolve 'Lisbon' to a locationKey, then call /forecasts/v1/daily/5day/{locationKey} and return the high and low for each of the next 5 days ### Weather-Aware Field Operations A logistics dispatcher uses the geoposition search and alerts endpoints to flag deliveries entering an active severe weather zone. The system geocodes each delivery address externally, calls /locations/v1/geoposition/search for the locationKey, and queries /alerts/v1/{locationKey}. Drivers get a heads-up rather than discovering hazards en route. Example prompt: For each delivery in tomorrow's schedule, look up the locationKey and return any active alerts as a routing risk flag ### Outdoor Activity Planning with Lifestyle Indices A running app shows a 'running index' for the user's location each morning, sourced from /indices/v1/daily/5day/{locationKey}. The app picks the running-specific index and renders a 5-day strip. Compared to showing raw temperature, the index combines temperature, humidity, wind, and air quality into a single planning signal. Example prompt: Retrieve the 5-day running index for a user's home locationKey and return the day with the highest score ### Agent-Driven Weather Lookup via Jentic An AI assistant in a calendar app answers 'what's the weather for my meeting in Berlin tomorrow?' by calling AccuWeather through Jentic. The agent searches for the right operation, resolves the location, and returns the forecast. The apikey query parameter is injected by Jentic at execution time. Example prompt: Through Jentic, search 'get the current weather for a city', resolve Berlin, and return current conditions plus tomorrow's daily forecast ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /locations/v1/cities/search | Search cities by name to resolve a locationKey | | GET | /locations/v1/geoposition/search | Resolve latitude and longitude into a locationKey | | GET | /currentconditions/v1/{locationKey} | Current weather conditions for a location | | GET | /forecasts/v1/daily/5day/{locationKey} | 5-day daily forecast | | GET | /forecasts/v1/hourly/12hour/{locationKey} | 12-hour hourly forecast | | GET | /alerts/v1/{locationKey} | Active severe weather alerts | | GET | /indices/v1/daily/5day/{locationKey} | Daily lifestyle indices | ## Key resources - **Locations** — Resolve city names and geocoordinates into AccuWeather locationKeys - **Current Conditions** — Retrieve current weather for a locationKey - **Forecasts** — Daily 5-day and hourly 12-hour forecasts keyed off locationKey - **Alerts** — Active severe weather alerts for a locationKey - **Indices** — Daily lifestyle indices (running, allergy, beach, and more) for a locationKey ## Why Jentic - **Setup:** Wiring the AccuWeather API by hand means appending the apikey query parameter on every call and resolving a location key before you can read conditions or forecasts. Through Jentic you install once, import the AccuWeather API from the API Directory, store the API key once, and your agent calls it. - **Permission scoping:** These endpoints are read-only lookups that take the location key in the URL or query, so limit the agent to the operations it needs, such as searching for a city and reading current conditions. You choose the operations it may call, so forecast, alert, or index reads are not included unless you add them. - **Credential handling:** Your AccuWeather API key is stored once, encrypted, by your own Jentic One instance and injected as the apikey query parameter at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'get the current weather for a city', and Jentic returns the location-search and current-conditions operations with their parameter schemas so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **OpenWeatherMap API** — Free-tier-friendly global weather API with current, forecast, and historical data. - **WeatherAPI.com** — Forecast and historical weather API with simple location string lookup. - **AccuWeather Core Weather API** — A leaner cut of AccuWeather endpoints focused on locations, current conditions, and forecasts. ## FAQ ### Why is there no official OpenAPI spec for AccuWeather API? AccuWeather does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AccuWeather API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the AccuWeather API use? An apikey query parameter on every request. Through Jentic, the key is stored encrypted in the vault and injected at execution time, so the raw key value never appears in the agent's context. ### How do I get the weather for a city with the AccuWeather API? Two steps. First call GET /locations/v1/cities/search with the city name to get a locationKey, then call GET /currentconditions/v1/{locationKey} or GET /forecasts/v1/daily/5day/{locationKey}. The locationKey is stable, so cache it per location to avoid repeating the lookup. ### What are the rate limits for the AccuWeather API? The OpenAPI spec does not document explicit rate limits - they are tied to your AccuWeather plan tier (free, standard, prime, elite). Implement exponential backoff on HTTP 429 and check your plan's daily call quota in the AccuWeather developer portal. ### How do I get a 5-day forecast through Jentic? Run pip install jentic, then search 'get the 5-day forecast for a city'. Jentic returns the locations search and forecast endpoints. Resolve the city, then call /forecasts/v1/daily/5day/{locationKey}. The apikey is injected by Jentic at execution time. ### Does the AccuWeather API include severe weather alerts? Yes. GET /alerts/v1/{locationKey} returns active alerts from official sources for the given location. Coverage and alert categories vary by region - North American and European coverage tends to be denser than less monitored areas. ### Can I limit what my agent is allowed to do with the AccuWeather API? Yes. Because Jentic One is self-hosted, you decide which of the read-only AccuWeather operations your agent may call, so you can allow it to search for a city and read current conditions while withholding the daily forecast, hourly forecast, alerts, and lifestyle index reads. Since every one of these endpoints only takes a location key in the URL or query and returns data, scoping the agent to just the operations it needs means it cannot reach the rest. Your own rules govern both the permitted operations and the API key that lets them run.