WeatherAPI.com Review: Weather, Geolocation & More

What WeatherAPI.com does and who it is for

WeatherAPI.com is a hosted weather and geolocation data service that exposes a broad set of JSON endpoints behind a single account. Rather than focusing on one data type, it groups several related categories — current conditions, forecasts, historical records, future projections, marine data, air quality, astronomy, time zone, IP lookup and sports schedules — into one API surface. For developers, that consolidation is the main appeal: you authenticate once and can pull from any of these endpoints without integrating multiple providers.

The service is squarely aimed at application developers who need weather context inside their products — anything from a dashboard widget or a mobile app to backend logic that adjusts behavior based on conditions or location. On the APIMemo directory it is one of the most-subscribed weather APIs, with 51,718 marketplace subscribers and a popularity score of 9.9 out of 10, so it is a well-trodden choice rather than a niche experiment.

Key capabilities and endpoint walkthrough

All endpoints return JSON and follow a consistent /{resource}.json naming pattern, which keeps the integration predictable across data types. The 20 listed endpoints cover the following resources:

• Realtime weather (GET /current.json) — current conditions for a queried location.
• Forecast weather (GET /forecast.json) — forecast data; the provider advertises up to 14-day hourly and 15-minute forecasts.
• History weather (GET /history.json) — historical hourly and 15-minute weather, documented as available from 1 January 2010 onwards.
• Future weather (GET /future.json) — projections up to 365 days ahead.
• Marine weather (GET /marine.json) — marine-specific conditions.
• Astronomy (GET /astronomy.json) — sun and moon data.
• Time zone (GET /timezone.json) — time zone information for a location.
• IP lookup (GET /ip.json) — geolocation from an IP address.
• Search / autocomplete (GET /search.json) — location search to resolve user input into queryable locations.
• Sports (GET /sports.json) — sports schedule data.
• Alerts (GET /alerts.json) — global weather alerts.

The provider also lists air quality data and a Map API described as "coming soon." The search.json endpoint is worth highlighting for practical builds: location resolution is usually the first step in any weather UI, and having autocomplete from the same vendor avoids gluing in a separate geocoder.

The consistent JSON-over-GET design means most endpoints can be exercised with a single query string containing your API key and a location parameter, which makes prototyping fast and keeps client code thin.

Pricing breakdown

WeatherAPI.com uses a freemium model. On APIMemo two plans are listed, both at $0 per month, distinguished mainly by daily request allowance and rate limiting:

The BASIC tier's 250 requests per day is enough for development, testing and very low-traffic projects. The MEGA plan doubles the daily allowance to 500 requests, adds a defined 10-requests-per-second rate limit, and — importantly — allows overage at $0.0010 per request once you exceed the daily quota. That overage pricing is what turns the free MEGA plan into a usable production option: you are not hard-capped, you simply pay a small per-call fee for traffic beyond the included allowance.

For anything beyond hobby-scale usage, the per-request math matters. At $0.0010 per call, every additional 1,000 requests costs $1, so it is straightforward to estimate monthly cost from your expected call volume. Caching responses — especially for current conditions and forecasts that do not change second-to-second — is the obvious lever to keep that bill down.

Practical use cases

The breadth of endpoints supports a range of builds:

• Consumer weather features — combine search.json for location entry, current.json for now-casting, and forecast.json for the days ahead.
• Historical analysis — history.json back to 2010 supports trend reporting, backtesting, or correlating past weather with business metrics.
• Planning tools — future.json up to 365 days out suits event or travel planning interfaces.
• Location-aware personalization — ip.json lets a web app infer a visitor's approximate location to pre-fill weather without asking for permission.
• Safety and notifications — alerts.json enables warning banners or push notifications based on official weather alerts.
• Specialized contexts — marine.json for boating or coastal apps, astronomy.json for sunrise/sunset and moon-phase features, and sports.json for schedule overlays.

Limitations and things to check before integrating

A few operational figures on APIMemo are worth weighing. The average latency is recorded at 122 ms, which is reasonable for a synchronous API call. More notable is the average success rate of 81.00% — meaningfully below a perfect score — so build defensive handling around failed or non-200 responses, with retries and sensible fallbacks rather than assuming every call succeeds. Note this is a directory-measured figure and differs from the up-to-99.99% uptime the provider advertises; test against your own usage patterns before relying on it.

Other points to confirm during evaluation:

• Request budgeting. Both listed plans are free but capped at 250 or 500 daily requests. Map your expected traffic against those limits and the $0.0010 overage rate early so costs do not surprise you.
• Rate limiting. The MEGA plan's 10 requests per second is generous for most apps but relevant if you fan out many concurrent calls; throttle on your side accordingly.
• Coming-soon features. The Map API is listed as not yet available, so do not design around it.
• Documentation depth. The full API documentation lives at weatherapi.com/docs/, which is where you should verify exact request parameters and response fields for each endpoint.

Getting started

Getting going is a matter of creating an account, obtaining an API key, and appending it to a GET request against the relevant endpoint. Because every resource shares the /{resource}.json convention, a working call to current.json is essentially a template for forecast.json, history.json and the rest — swap the path and adjust parameters. Start on the BASIC plan to validate response shapes and confirm the data fits your feature, then move to the MEGA plan when you need the higher daily allowance, the explicit rate limit, or the pay-as-you-go overage that supports production traffic. Consult the official documentation for the precise parameter list and field-level response details before wiring anything into production.