The Weather Company Data APIs vs Weatherbit API

The Weather Company Data APIs

A wide weather data API with 168 API references built from OpenAPI documents, global 4 km current conditions, hourly history from June 2015 and a status page with component history. Keys come only through a sales-reviewed trial or contract, travel only in the URL, and the terms that govern the API are not published.

Weatherbit API

A read-only weather API with a Swagger 2.0 spec, quota headers on every response and a status page showing 100 per cent on three API monitors over 90 days. The key travels only in the query string, the free plan allows 50 requests a day for non-commercial use, and the last dated API announcement is 1 August 2025.

The Weather Company Data APIs

1. Send units, language and format=json with a location on every v3 call, plus Accept-Encoding: gzip, which the usage guide marks as required.
2. Keep the key out of logs and client-side code, because it travels in the query string as apiKey.
3. Treat a 401 as either a bad key, an endpoint outside the key's package or an exceeded limit, and treat a 204 as no data for the query.
4. Each forecast duration (3day to 15day) is a separate entitlement. Request only durations the contract covers.
5. Use /v3/aggcommon to combine up to 10 products in one request. Each product and each location still counts as one call.

Weatherbit API

1. Pass lat and lon. City, postal code and station lookups are accepted, but the docs recommend coordinates and mark station ID as use with caution
2. Read X-RateLimit-Remaining and X-RateLimit-Reset on each response. Daily quotas reset at 00:00 UTC and a spent quota returns 429 until then
3. Treat HTTP 204 with an empty body as no data found, not as an error
4. Split historical requests into ranges of one month or less. History needs the Plus plan or higher and has its own daily quota
5. Keep the key out of logs. It is part of the URL on every call, so always use https://api.weatherbit.io/v2.0