canonical: https://jentic.com/apis/accuweather.com/accuweather-core-weather-api

# AccuWeather Core Weather API

Jentic publishes the only available OpenAPI specification for AccuWeather Core Weather API, keeping it validated and agent-ready. This is the focused core cut of AccuWeather's data services, exposing 8 endpoints across location resolution, current conditions, and 1-day, 5-day, and 12-hour forecasts. Locations can be resolved by city search, autocomplete, or geoposition, and weather data is keyed by the resulting locationKey. The API uses an apikey query parameter for authentication and is hosted at dataservice.accuweather.com.

## For AI agents

Resolve a location and retrieve current conditions, 1-day or 5-day daily forecasts, and 12-hour hourly forecasts from AccuWeather core endpoints so agents can deliver weather information for any global location.

## Scope

Does not handle severe weather alerts, lifestyle indices, radar tiles, or historical archives - use for location resolution and current/daily/hourly forecasts on AccuWeather only.

## Capabilities

- Search cities by name with full text or autocomplete to resolve a locationKey
- Resolve a latitude/longitude pair into a locationKey via geoposition search
- Retrieve location detail by locationKey for display name, country, and timezone
- Retrieve current weather conditions at a locationKey
- Retrieve a 1-day daily forecast for short-horizon planning
- Retrieve a 5-day daily forecast for trip-style planning
- Retrieve a 12-hour hourly forecast for the next half-day

## Use cases

### Autocomplete-Driven Location Picker

A weather widget powers a city autocomplete using GET /locations/v1/cities/autocomplete. Each keystroke calls the endpoint with the partial query and renders matching cities. When the user picks one, the locationKey is cached and used for subsequent forecast calls. The autocomplete keeps the picker responsive and avoids requiring users to type full city names.

Example prompt: Call /locations/v1/cities/autocomplete with the partial query 'San Fr' and return the top 5 matching cities with their locationKeys

### 1-Day Forecast for Same-Day Decisions

A logistics dashboard shows a 1-day forecast for each route start city using GET /forecasts/v1/daily/1day/{locationKey}. Operators glance at the day's high, low, and precipitation chance to triage routes before dispatch. This is lighter than a 5-day pull and fits the same-day decision horizon.

Example prompt: For each route's start city, retrieve the 1-day daily forecast and flag any with precipitation probability above 60%

### Event Venue Weather at Coordinates

An event app stores venue coordinates rather than addresses. Weather lookup goes through /locations/v1/cities/geoposition/search to resolve a locationKey and then /forecasts/v1/hourly/12hour/{locationKey} for the event window. The flow handles outdoor festivals and pop-ups where there may be no canonical city name. Hourly precision lets organizers plan tent setup vs pack-up time.

Example prompt: Resolve venue coordinates to a locationKey and return the next 12 hours of hourly forecast

### Agent-Driven Weather Lookup via Jentic

An AI travel assistant calls AccuWeather Core Weather through Jentic to answer 'what's the weather in Reykjavik this weekend?' The agent searches for the right operation, resolves the city, and returns the 5-day forecast. The apikey lives in your Jentic One instance and is added at execution time.

Example prompt: Through Jentic, search 'get the 5-day forecast for a city', resolve Reykjavik, and return the daily highs, lows, and precipitation

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /locations/v1/cities/search | Search cities by full name |
| GET | /locations/v1/cities/autocomplete | Autocomplete city names from partial input |
| GET | /locations/v1/cities/geoposition/search | Resolve coordinates into a locationKey |
| GET | /locations/v1/{locationKey} | Retrieve detail for a locationKey |
| GET | /currentconditions/v1/{locationKey} | Current weather conditions |
| GET | /forecasts/v1/daily/1day/{locationKey} | 1-day daily forecast |
| GET | /forecasts/v1/daily/5day/{locationKey} | 5-day daily forecast |
| GET | /forecasts/v1/hourly/12hour/{locationKey} | 12-hour hourly forecast |

## Key resources

- **Locations** — City search, autocomplete, geoposition search, and locationKey detail lookup
- **Current Conditions** — Current weather for a resolved locationKey
- **Forecasts** — 1-day and 5-day daily forecasts and 12-hour hourly forecasts keyed by locationKey

## Why Jentic

- **Setup:** Wiring the AccuWeather Core Weather API by hand means appending the apikey query parameter on every call and resolving a location key before requesting current conditions or forecasts. Through Jentic you install once, import the AccuWeather Core Weather 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 its 5-day forecast. You choose the operations it may call, so hourly or current-conditions 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 5-day forecast for a city', and Jentic returns the city-search and forecast operations with their parameter schemas so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **AccuWeather API** — Full AccuWeather surface that adds severe weather alerts and daily lifestyle indices.
- **OpenWeatherMap API** — Free-tier-friendly weather API with current, forecast, and historical data.
- **WeatherAPI.com** — Single-call weather API by city or coordinates without a separate location resolution step.

## FAQ

### Why is there no official OpenAPI spec for AccuWeather Core Weather API?

AccuWeather does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AccuWeather Core Weather 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 Core Weather 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 value stays out of agent context.

### How do I get a 5-day forecast for a city?

Two calls. First GET /locations/v1/cities/search with the city name to obtain a locationKey, then GET /forecasts/v1/daily/5day/{locationKey}. Cache the locationKey per city - it is stable across calls.

### What are the rate limits for the AccuWeather Core Weather API?

The OpenAPI spec does not document explicit rate limits. Limits are tied to the AccuWeather plan tier (free, standard, prime, elite) and are documented in the AccuWeather developer portal. Implement exponential backoff on HTTP 429.

### How is this different from the AccuWeather API entry on Jentic?

The Core Weather API is the leaner cut focused on locations, current conditions, and forecasts (1-day, 5-day, hourly). The full AccuWeather API entry adds severe weather alerts and lifestyle indices. Pick this one when alerts and indices are not needed.

### How do I look up weather by coordinates through Jentic?

Run pip install jentic, then search 'resolve coordinates to a weather forecast'. Jentic returns /locations/v1/cities/geoposition/search and the forecast endpoints. The apikey is injected at execution time, so you only supply the coordinates and locationKey.

### Can I limit what my agent is allowed to do with the AccuWeather Core Weather API?

Yes. Because you run Jentic One yourself, your own rules decide which of these read-only lookups the agent may call, so you can grant just the operations it needs, such as searching for a city and reading its 5-day daily forecast. If you do not add the current-conditions, 1-day, or 12-hour hourly endpoints, the agent cannot invoke them. Your AccuWeather API key is injected as the apikey query parameter at execution time and never enters the agent's context.