Set Up Custom HTTP Live Sync
Send live data into Meteobreeze from any system that can make HTTP requests.
Set Up Custom HTTP Live Sync
Use this guide if your device, script, or service can make HTTP requests and you want to send live observations directly to Meteobreeze.
This option is the most flexible. You send a GET request to the ingest URL and include the current observation values as query parameters.
When to use it
- You have a custom weather source or script
- Your software can make HTTP GET requests
- You want to send only the fields you have available
Before you start
- Create a live source in Meteobreeze
- Copy the ingest URL
- Know the timestamp and measurement values you want to send
Tag mapping
Custom HTTP lets you send the field names Meteobreeze expects directly. Use the canonical field names when your source already emits metric values.
| Meteobreeze field | Example meaning |
|---|---|
observedAt | Timestamp for the packet |
temperatureAvgC | Current or average temperature |
temperatureMaxC | Maximum temperature |
temperatureMinC | Minimum temperature |
dewPointAvgC | Dew point |
humidityAvgPct | Relative humidity |
windDirectionAvgDeg | Wind direction |
windSpeedAvg | Wind speed |
windGustMax | Wind gust |
pressureAvg | Pressure |
rainRateAvg | Rain rate |
rainTotalMm | Rain total |
solarRadiationAvg | Solar radiation |
uvIndexAvg | UV index |
If your source uses Fahrenheit, miles per hour, inches, or similar units, use the unit-specific aliases supported by Meteobreeze.
Step-by-step
- Copy the live ingest URL from Meteobreeze.
- Send a
GETrequest to that URL. - Include
observedAtin every packet. - Add any measurement fields you have available.
- Use a timezone-aware timestamp or unix milliseconds.
- Test the request and check the data sources page.
Example
GET /api/imports/live/your-ingest-key?observedAt=2026-04-20T18:30:00Z&temperatureAvgC=14.2&humidityAvgPct=71.4&windSpeedAvg=8.6The exact parameters you send depend on the values your source can provide.
Common issues
- If the request fails, check that
observedAtis present. - If the timestamp is wrong, make sure it includes a timezone or uses unix milliseconds.
- If Meteobreeze rejects a field, the parameter name may not be supported.
- If values are in Fahrenheit, miles per hour, or inches, use the unit-specific parameter names that Meteobreeze supports.
- If you are sending more than one alias for the same metric, keep only one in the packet.
FAQ
- Do I need to send every field? No. Send only the values you have.
- Can I mix canonical and converted fields? Yes, as long as the parameter names are supported.
Related pages
Image needed: a sample packet diagram showing observedAt plus a few live metric parameters being sent to the ingest URL.