To import weather data into WordPress, add a weather API as a provider in Ingestics, map the temperature, condition, and forecast fields to a post, and let a schedule keep the page fresh. The setup works on the Free tier with a manual fetch; Lite makes it fully automatic.

Local weather is a classic “content you would never maintain by hand” case: it changes hourly, readers expect it to be current, and the data is free from several APIs. Here is the complete workflow.

What do you need before you start?

Three things:

1. A weather API. OpenWeatherMap, WeatherAPI.com, and Open-Meteo all offer free plans that return JSON. Open-Meteo needs no key at all; the others give you one at signup.
2. The endpoint URL for current conditions or forecast, with your city and units in the query string (most APIs take a units=metric or imperial parameter).
3. Ingestics Free installed — 3 API providers, which covers a three-city weather page.

How do you connect a weather API to WordPress?

In Ingestics → Providers, add a new API provider (or use the Guided Setup Wizard). Paste the endpoint URL with your query parameters, choose GET, and set authentication: API key for OpenWeatherMap and WeatherAPI.com, none for Open-Meteo. Credentials are stored encrypted, and previews mask them.

Then open the call preview. You should see the raw JSON — current temperature, a conditions string, humidity, wind. A 401 here means the key is wrong or not yet activated (some weather APIs take a few minutes to activate new keys).

How do you map weather fields to a post?

Weather JSON is flat and simple, which makes mapping quick. Typical OpenWeatherMap paths:

• name → part of the post title (“Weather in London”)
• main.temp → content
• weather.0.description → content (“light rain”)
• main.humidity, wind.speed → content

On Free, basic JSON-path mapping composes the post. Lite adds the Post Template Builder, which lets you lay out title, content, and excerpt with placeholders — worth it once you want a readable sentence like “18°C and partly cloudy in London, humidity 64%”.

Should each fetch create a new post or update one?

Decide this early:

• New post per fetch — right for a daily forecast archive (“Forecast for July 27”). Duplicate detection on all tiers stops accidental re-posts of the same fetch.
• One live post that updates — right for a “Current conditions” page. That needs Pro’s Advanced Sync Engine, which matches existing posts (by source URL, external ID, or title) and updates them in place instead of stacking new posts.

Most weather pages want the second pattern; a daily-forecast blog wants the first.

How often should weather data update?

Lite’s scheduled fetching handles this — hourly is the sweet spot for current conditions, and it stays comfortably inside free API quotas (OpenWeatherMap’s free plan allows 1,000 calls/day; 24 hourly calls per city uses 2.4% of that). Pro adds custom frequencies if you want tighter cadence around, say, storm coverage.

How do you display weather on your site?

Lite unlocks the frontend layer: the [auto_api_feed] shortcode, the Gutenberg block, template tags, and a grid layout. A three-city grid — one provider per city, one card per city — makes a clean regional weather page. Shortcode attributes are in the documentation.

What about multi-city dashboards?

Each city is its own provider with its own endpoint. Free covers 3 cities (3 API providers), Lite covers 10, Pro 25, and Business is unlimited — enough for a full regional network. Give each provider its own category so city pages can filter cleanly.

Which Ingestics tier does this workflow need?

• Free — up to 3 cities, manual fetch, basic mapping. Enough to prove the pipeline.
• Lite — scheduled hourly updates, template builder, frontend display. The practical minimum for a live weather page.
• Pro — sync-in-place updates for a single live conditions post, custom frequencies.

Weather is one of several live-data feeds Ingestics handles the same way — see stock market data and sports scores, the underlying REST API import guide, or the use cases hub for more automated publishing workflows.