AccuWeather API

Implementation notes

When to use AccuWeather API

AccuWeather is the right choice when forecast accuracy is more important than call volume — its MinuteCast (minute-by-minute precipitation for 2 hours) and 45-day extended forecasts are genuinely differentiated from commodity weather APIs. The tradeoff is a 50-call/day free tier that only suits low-traffic widgets or prototypes.

Common pitfalls

• AccuWeather uses its own location key system. Before fetching a forecast, you must first call the Locations API to resolve a city name or coordinates to an AccuWeather location key. This means every weather lookup costs two API calls, cutting your effective free tier to 25 unique locations per day.
• The `demo` key in AccuWeather's documentation is non-functional for most endpoints. Some examples show `apikey=...` with a placeholder that returns a 401 immediately.
• AccuWeather returns temperatures in both Fahrenheit and Celsius in a single response (the `Value` and `Unit` fields are nested inside a `Temperature` object), but the default unit system depends on country. Explicitly request `details=true` and parse the unit field rather than assuming.
• The free plan does not include RealFeel Shade temperature, which AccuWeather prominently markets. That field returns `null` unless you have a paid plan.

Quick start (bash)

# Step 1: get location key
curl "http://dataservice.accuweather.com/locations/v1/cities/search?apikey=YOUR_KEY&q=Paris"
# Step 2: get forecast with the returned location key
curl "http://dataservice.accuweather.com/forecasts/v1/daily/1day/623?apikey=YOUR_KEY"

Embed this badge

Add a live status badge to your README, docs, or website.

Markdown

[![AccuWeather API Status](https://freeapi-builder.a10ayassine.workers.dev/badge/accuweather.svg)](https://freeapi.watch/accuweather)

HTML

<a href="https://freeapi.watch/accuweather"><img src="https://freeapi-builder.a10ayassine.workers.dev/badge/accuweather.svg" alt="AccuWeather API Status"/></a>