Google Weather API (Maps Platform) vs The Weather Company Data APIs

Google Weather API (Maps Platform)

Covered by the Maps Platform SLA, 99.9 per cent with service credits. History is 24 hours only, and bulk data isn't available.

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.

Google Weather API (Maps Platform)

1. Ask for only the days or hours you need, one location a call. Every call is one billable event
2. Page with pageSize and pageToken rather than asking for 240 hours at once
3. Check the coverage page before promising alerts. Coverage is by country
4. Refetch rather than cache. The Maps terms give no caching window for weather content
5. Restrict the key to the Weather API and your server IPs in the Cloud console

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.