In development · Commercial API · New Zealand and Australia

Nowcast API

A six-hour forecast of air temperature and wind for a named weather station in New Zealand or Australia, updated every 10 minutes.

The Nowcast API is in development and not yet generally available. We're planning a closed beta with commercial energy teams in New Zealand and Australia. Wind speed and direction are in development.

For commercial use only. For personal projects, research and learning, see the free tier of the Weather Stations API.

Request commercial access Read the API docs
Example response

What it's for

The Nowcast API is for forecasting teams whose decisions depend on the next few hours, such as teams forecasting demand, load and dispatch in the energy sector. It's built with machine learning from the station's latest observations.

A new forecast every 10 minutes

Each forecast covers the next six hours in 36 steps, 10 minutes apart. A new one runs when the station reports a new observation, targeted at about 2 minutes past each 10-minute mark. Each forecast is labelled with its model_run_time, the time of its first step.

Forecasts for named stations

Each forecast is for one observation station, addressed by the station's WMO ID, the same identifier the Weather Stations API uses. Air temperature is forecast as the station's 1-minute mean, the same observation the model is trained and verified against.

Testing it beside a current forecast

We haven't published accuracy figures yet. The API can run alongside an existing forecast feed, so a forecasting team can score it against its own forecast error.

Who it suits

It's for organisations in New Zealand and Australia that run their own forecasting or operational models and have a developer to connect an API. It's built for uses where hourly forecast data is too coarse.

  • The main ones are energy trading, and demand and load forecasting.
  • Network operations and short-interval dispatch, such as batteries and virtual power plants, may also be a fit.

MetService supplies the weather forecast for the station, and the customer's own model turns it into demand, load, generation or a dispatch decision.

Not included

  • Rain, wind gusts, maps or grids, forecasts beyond six hours, several locations in one request, and dashboards.
  • A free or non-commercial tier. For personal projects, research and learning, see the free tier of the Weather Stations API.

  • 6 hours

    Forecast horizon

  • 10 minutes

    Between steps

  • 36 steps

    In every forecast

  • NZ & AU

    Selected stations

Built for your developers

Responses are JSON over HTTPS, and the API key is sent as a bearer token in the Authorization header. Errors use RFC 9457 fields, units are given for each variable in the response metadata, and null means no value is available for a step. A /health endpoint reports the API's status.

How access works

  1. Tell us the stations you need. Request commercial access and name the stations or sites, and tell us whether they're on our network or yours.
  2. We check the observations. Stations on our network are already quality-checked. Using your own stations is in development. For those, we review at least a year of your historical observations to make sure they're good enough to train a forecast on, then connect your live feed.
  3. We train a model for each station. Every station gets its own nowcast model, trained on that station's observations. Your own stations take longer to set up than ours.
  4. Poll the endpoint. Each API key is authorised for the agreed stations, and each request returns one of them.

Requesting access starts a conversation with our team about your stations and where the API is up to.

Example response

Full API reference
GET /nowcast/v1/locations/93110
curl -H "Authorization: Bearer <your-api-key>" \
  "https://api.forecast.metservice.com/nowcast/v1/locations/93110"
{
  "metadata": {
    "location": { "id": "93110", "latitude": -37.0089507, "longitude": 174.8071985 },
    "model_run_time": "2026-09-29T01:30:00Z",
    "units": {
      "air_temperature_1min_mean": "degC",
      "wind_speed_1min_mean": "kn",
      "wind_from_direction_1min_mean": "degrees_true"
    }
  },
  "nowcast_data": [
    { "time": "2026-09-29T01:30:00Z", "air_temperature_1min_mean": 15.7, "wind_speed_1min_mean": 12.4, "wind_from_direction_1min_mean": 230 },
    { "time": "2026-09-29T01:40:00Z", "air_temperature_1min_mean": 15.8, "wind_speed_1min_mean": 13.1, "wind_from_direction_1min_mean": 235 },
    { "time": "2026-09-29T01:50:00Z", "air_temperature_1min_mean": 15.6, "wind_speed_1min_mean": 12.8, "wind_from_direction_1min_mean": 232 }
  ]
}

93110 is the WMO ID for Auckland Airport, the same identifier the Weather Stations API uses. This shows the response at general availability, with 3 of the 36 steps. The wind fields are planned and may change before release. Values are illustrative. null means no value is available for a step.

Specifications

In development, not yet generally available. Specifications, variables and response formats may change before general availability.

Variables
Air temperature (°C). Mean wind speed (knots) and wind direction, in development.
Values
Each step is a forecast of the station's 1-minute mean air temperature at the step's time, the same observation the model is trained and verified against
Units
Given for each variable in the response metadata. Air temperature is in degC
Not included
Wind gusts, rain, humidity, dew point, solar radiation
Forecast horizon
6 hours, in 36 steps of 10 minutes
Update frequency
A new forecast every 10 minutes, targeted at about 2 minutes past each 10-minute mark, when a new observation has arrived
Forecast height
The station's sensor height: typically 2 metres for air temperature, and 10 metres for wind (in development)
Coverage
Selected stations in New Zealand and Australia
Locations per request
One. Each API key is authorised for an agreed set of stations
Location IDs
The station's WMO ID, the same identifier the Weather Stations API uses. ICAO IDs aren't accepted
Format
REST, JSON over HTTPS
Base URL
https://api.forecast.metservice.com/nowcast/v1
Endpoints
GET /locations/{location_id}, and GET /health for a status check
Authentication
API key in the Authorization header: Bearer <your-api-key>
Errors
RFC 9457 fields: type, title, status, detail
Use
Commercial use only
Full specifications in the API docs

Limits

Accuracy. We haven't published verification results yet. Until we do, a forecasting team can judge it by running it beside a current feed and scoring it against its own forecast error. We'll publish verification results when they're available.

Horizon. Forecasts cover the next six hours. For longer horizons, use it alongside a longer-range forecast.

Wind gusts. Gusts aren't included and aren't planned for launch. Wind, when it's added, will be mean wind only, so it isn't suitable for gust-based limits such as turbine cut-out or closure thresholds.

  • Rain. Precipitation isn't part of this product.
  • Locations per request. Each request returns one location.
  • Observations. A new forecast runs only when the station reports a new observation.
  • Format. It's a REST API returning JSON time series, with no dashboard. It needs a developer to integrate.

Questions

Can I use this for a personal or non-commercial project?

No. The Nowcast API is for commercial use only, and there's no free tier. The free tier of the Weather Stations API is a better fit for personal projects, research and learning.

What does it cost?

It's priced per location. We don't publish a price, and we talk pricing through with each organisation.

How accurate is it?

We haven't published verification yet. You can run it alongside your current feed, on your stations, and score it against your own forecast error. We'll share our verification results when they're done.

Is wind available?

Not yet. Wind speed and direction are in development. The published specification covers air temperature.

Which locations can I get?

Selected observation stations in New Zealand and Australia. Tell us the stations or sites you need when you request access, and we'll confirm what's available.

Do I have to replace my current forecast provider?

No. It covers the next six hours and is designed to be used alongside a longer-range forecast, as an input to the models a team already runs, such as load forecasting, trading, network operations or short-interval dispatch.

What happens if the station stops reporting?

Missing values are returned as null inside a complete response, and a new forecast runs only when a new observation arrives.

Can I get several locations in one call?

No. Each request returns one location, and each key is authorised for an agreed set of stations.

Do I need my own developer?

Yes. It's a REST API returning JSON, with no dashboard.

When will it be generally available?

We haven't set a date. Everyone who requests commercial access will hear from us when it launches.

Commercial access

The Nowcast API is in development and isn't on sale yet. If your organisation would use it, tell us what the forecast would feed and which stations or sites you need. We'll reply with where the API is up to, and whether a place in the closed beta fits.

Commercial enquiries only. For personal projects, research and learning, see the free tier of the Weather Stations API.

Request commercial access

Requesting access starts a conversation with our team. Keys aren't issued from this form. The form covers all our APIs, so choose Nowcast API and tell us what you'd use it for.

To discuss pricing or contract terms first, contact our team.

The Nowcast API is provided by MetService, New Zealand's national meteorological service.

The Nowcast API is for commercial use only. It doesn't include wind gusts and isn't suitable for gust-dependent safety decisions. Specifications, variables and response formats may change before general availability.