Push readings as JSON

The personal upload URL speaks the Ecowitt and Wunderground protocols, which covers every commercial station. If you are sending readings from something else - a script, a Raspberry Pi, a home-built sensor, an industrial logger - you can POST JSON to the same URL instead.

Send it to your ingest URL with a JSON content type:

curl -X POST https://i.pro-weather.com/i/YOUR-INGEST-TOKEN \
  -H 'Content-Type: application/json' \
  -d '{
    "units": { "temperature": "C", "windspeed": "kph", "rainfall": "mm", "pressure": "hPa" },
    "lastupdated": "2026-08-07T14:30:00Z",
    "temperature": { "outdoor": 18.4, "indoor": 21.0 },
    "humidity":    { "outdoor": 67 },
    "wind":        { "speed": 11.2, "direction": 213, "gust10m": 24.0 },
    "rain":        { "counter": 3.4, "rate": 0.0 },
    "pressure":    { "sealevel": 1013.2, "absolute": 998.4 },
    "solar":       { "irradiation": 286, "uvi": 2 }
  }'

You get back success when the reading was accepted.

You declare the units

This is the part that matters. Every other upload protocol fixes its units into the field names, so tempf is always Fahrenheit whether you like it or not. Here you say what you are sending, and we convert.

A reading with no declared unit is dropped, not guessed. If you send a temperature of 20 and no units.temperature, we do not assume: read as Fahrenheit that is a 31-degree error, and a station that is quietly 31 degrees wrong is worse than one showing nothing. The rest of the payload still lands. The same applies to a unit we do not recognise.

Fields

Everything is optional except that you must send at least one real reading. Anything you leave out is treated as "no sensor", not as zero.

Multi-channel sensors are arrays, each entry carrying its own index (1-16):

Notes

• Dew point, feels-like, wind chill, heat index and cloud base are derived for you from temperature, humidity and wind. Send them only if you have measured them; anything you send wins over the calculated value.
• Readings outside a plausible range for the sensor are dropped individually, so one stuck channel cannot poison a whole upload.
• Post as often as you like. Readings are archived at roughly five-minute intervals, matching the rest of the platform, so a faster cadence gives you a livelier page without inflating your history.
• The envelope deliberately matches the JSON station format documented for CumulusMX, so if you already emit that payload you can point it here without changing anything.