The API returns null for hourly or daily values - why?
The Metry API supports three granularities for consumption data: month, day, and hour. Monthly values work for most metering points, but hourly and daily data can return null even when the endpoint is correct. This is by design, not a bug.
Why hourly and daily values may be null
Hourly and daily data is only available if:
- The utility provider delivers data at that resolution, and
- Hourly or daily collection has been ordered for that specific metering point.
Monthly data is the default and is available for almost all metering points. Hourly values require a separate order - either from the utility provider directly or via Metry - and come at additional cost in some cases.
How to check what granularity is available for a meter
In the Metry portal, open the metering point and look at the Collection section. It shows what resolution is currently being collected (monthly, hourly, or both).
You can also call the meters endpoint and inspect the metrics field to see which data types are available for a given meter.
How to order hourly or daily collection
- Contact support@metry.io and specify which metering point IDs you need hourly data for.
- We check whether the utility supports it and what steps are needed.
- If ordering from the utility requires a letter of authority, we will provide a template.
Some utilities only deliver monthly data regardless of what is requested. In those cases, hourly collection is not possible.
Example: correct API call for monthly data
GET https://app.metry.io/api/v2/consumptions/{key}/month/2026040100-2026050100?metrics=energy
Changing month to hour or day will return null for meters without hourly collection enabled:
GET https://app.metry.io/api/v2/consumptions/{key}/hour/2026040100-2026050100?metrics=energy
This is expected behavior. The API documentation notes that hourly and daily granularity is supported but not necessarily available for every meter.
Further help
See Introduction to Metry API or contact support@metry.io .