What Yahoo Weather does and who it is for
Yahoo Weather exposes weather data through a single endpoint path (GET /weather) that accepts three different location input methods. The API targets developers building applications that need location-based weather lookups — think travel apps, outdoor scheduling tools, local news widgets, or IoT dashboards. With nearly 10,542 active marketplace subscribers and a popularity score of 9.9 out of 10, it is clearly one of the most widely adopted weather APIs available in this marketplace.
The average latency sits at 864 ms, which is on the higher end compared to some alternatives. For user-facing, real-time interfaces, that round-trip time is worth factoring into your UX design — consider caching responses aggressively on your end. On the positive side, the reported average success rate is 100%, meaning reliability is not a concern based on observed data.
Endpoint walkthrough: three ways to query location
All three query methods share the same GET /weather path; the difference is in the query parameters you send.
1. Search by city name
Pass a location parameter with a human-readable city string. Examples from the documentation include location=sunnyvale,ca and location=shanghai,cn. The city-plus-region format keeps queries readable and is a natural fit for apps where users type in a city directly.
2. Search by WOEID
Yahoo's proprietary Where On Earth ID (WOEID) is a numeric identifier for specific geographic places. To find a WOEID, you navigate to the Yahoo Weather forecast page for a city and extract the ID from the URL. This approach is less convenient for dynamic lookups (users cannot intuitively supply a WOEID), but it is precise — useful when you have pre-mapped locations and want to eliminate ambiguity between cities that share a name.
3. Search by latitude and longitude
Pass lat and lon parameters as decimal numbers, e.g., lat=37.372&lon=-122.038. This is the most developer-friendly option for apps that already have geographic coordinates — from device GPS, a mapping API, or a geocoding layer — since it requires no prior lookup of Yahoo-specific identifiers.
All three methods hit the same underlying resource, so the response shape should be consistent regardless of which query type you use. The fact that there is no separate geocoding endpoint to call first (for the city-name and lat/lon paths) simplifies integration.
Pricing breakdown
Yahoo Weather uses a freemium billing model with four tiers. The free tier is genuinely free but very constrained; paid tiers scale up both monthly quotas and hourly rate limits.
| Plan | Monthly cost | Monthly requests | Hourly rate limit | Overage per request |
|---|---|---|---|---|
| BASIC | $0 | 50 | — | — |
| PRO | $5 | 50,000 | 1,000 / hr | $0.0004 |
| ULTRA | $10 | 120,000 | 2,000 / hr | $0.0002 |
| MEGA | $50 | 750,000 | 5,000 / hr | $0.0001 |
BASIC is best treated as a proof-of-concept or personal experimentation tier. Fifty requests per month works out to fewer than two requests per day on average — enough to validate a response schema or prototype a UI, but not enough to power any real user traffic.
PRO at $5/month is the natural starting point for a small production app. 50,000 monthly requests at 1,000 per hour is reasonable for low-to-medium traffic applications. If you go over the quota, overage charges are $0.0004 per request, so a spike of 10,000 extra calls would add $4 to your bill — manageable but worth monitoring.
ULTRA nearly triples the monthly quota (120,000) for only double the base price ($10), making the per-request cost more efficient than PRO for apps with predictable mid-volume usage. Overage drops to $0.0002.
MEGA is suited for high-volume production use — 750,000 requests per month at up to 5,000 per hour — with the lowest overage rate of $0.0001 per request. At $50/month, this is still economical compared to building weather data infrastructure independently.
Practical use cases
- Consumer apps: A travel planning app can use the city-name endpoint to show forecasts for user-searched destinations without requiring geographic coordinate lookups.
- IoT and embedded devices: Devices with GPS chips can query directly via lat/lon without any intermediate lookup step.
- Pre-mapped dashboards: Operations tools covering a fixed set of locations (warehouses, stores, field sites) can store WOEIDs at setup time and use the WOEID endpoint for clean, unambiguous queries.
- Content and media: News or lifestyle sites displaying localized weather widgets need relatively few requests per day, making the PRO plan a cost-effective fit.
Limitations and things to check before integrating
Free tier is very restrictive. Fifty requests per month sounds like a lot until you realize a single active user checking weather twice a day would exhaust the quota in under a month. Plan to upgrade to PRO from the start if you are building anything with real users.
Latency at 864 ms. Nearly a second of average response time means Yahoo Weather may not be appropriate for latency-sensitive real-time applications without a caching strategy. Implement a server-side cache keyed on location input and refresh it on a schedule (e.g., every 10–30 minutes) rather than making a live call per user request.
WOEID dependency. The WOEID system is Yahoo-proprietary. If you build around it, you are tied to Yahoo's location taxonomy. The lat/lon method is more portable if you ever want to swap providers.
No explicit auth method documented in the available data. Confirm authentication requirements (API key, OAuth) when signing up through the marketplace before writing integration code.
No documented endpoint for forecasts vs. current conditions. All three query variants point to the same /weather endpoint — inspect actual response payloads during testing to understand what time ranges and data fields are returned.
Getting started
- Subscribe via the marketplace (the BASIC plan is free and requires no payment method to trial).
- Make a test call using the city-name method with a known city to inspect the full response schema.
- Decide on your location-query strategy — city name for user-typed input, lat/lon for coordinate-based apps, WOEID for pre-mapped fixed locations.
- Implement a caching layer before going to production to reduce request volume and smooth out latency.
- Estimate your monthly request volume and choose the plan whose included quota covers your expected usage, keeping overage rates in mind for traffic spikes.
With a 100% success rate and a large active subscriber base, Yahoo Weather is a low-risk choice from a reliability standpoint. The main variables to weigh are the tight free-tier quota and the sub-second latency, both of which are solvable with thoughtful architecture.
