ApivomApivom
Get Demo

Google Pollen API Connector

Google's Pollen API — a daily forecast of grass, tree and weed pollen with per-plant indexes, health recommendations and map tiles for any location — registered in Apivom Atlas for health, outdoor-services and real-estate tenants, with your own Maps Platform key.

What you can do

  • Forecast lookup: up to five days of pollen indexes by type (grass, tree, weed) and by plant, with seasonality and health recommendations
  • Heat-map tiles to render pollen layers on a map
  • Both routes read-only; coverage in 65+ countries per Google's documentation
  • Registered in Atlas with the credential contract and the AI integration guide (llms.txt)

Use cases

  • Plan outdoor work around allergy peaks — Check the five-day pollen forecast for a site before scheduling landscaping or outdoor events with staff who have allergies.
  • Pollen context on properties and venues — Show today's grass, tree and weed indexes for a location on listing or venue pages, with Google's health recommendations.

The Pollen API on pollen.googleapis.com is a Google Maps Platform environment service that forecasts airborne pollen for a coordinate: for up to five days it returns the Universal Pollen Index for grass, tree and weed pollen, a breakdown by plant species with whether each is in season, plain-language health recommendations, and descriptive metadata such as the plant's picture and cross-reactions. A second route serves heat-map tiles so a pollen layer can be drawn over a map. Apivom Atlas registers both read-only routes with the Maps Platform credential contract, per-tenant logging and the AI integration guide (llms.txt); your key, project and quotas apply. No Apivom product workflow uses pollen data today — the connector is available to tenants in health, landscaping, outdoor services or property who want to build on it, and a product flow is scoped per customer.

Authentication

Your own Google Cloud API key (Maps Platform) with this API enabled on the project; the Apivom product sends it as the x-goog-api-key header on each call. Google bills the project that owns the key. The key is encrypted in your Iris tenant; Apivom Atlas stores nothing.

Frequently asked questions

Can I switch this connector on today?

The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.

How far ahead does the forecast go, and for which plants?

Up to five days per request. Each day carries indexes for the three pollen types and, where available, per-plant detail (for example birch, olive, ragweed) with an in-season flag and recommendations.

Which Google Cloud project pays for the calls?

The project that owns the API key you connect. Enable this specific API on that project, restrict the key to the APIs you actually use, and Google's Maps Platform pricing and monthly credit apply to it directly — Apivom adds no charge and shows every call in your tenant's integration log.

Does Apivom charge per API call for this connector?

No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.

Where are my credentials stored and who can see the traffic?

Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.

More Atlas integrations

AI integration guide (llms.txt)

Machine-readable markdown — feed it to your AI assistant as integration instructions.