Traffic
https://api.butlr.io/api/v3/reporting
Traffic measures the flow of people entering and leaving a space. It tracks entries (Ins) and exits (Outs), providing data that can be aggregated or filtered by floors, rooms, or zones. This metric relies on traffic sensors placed at key access points to monitor movement over time accurately.

Response fields
Traffic responses contain per-bucket counters and, since August 3, 2026, their cumulative counterparts:
in
Entries counted during the time bucket
out
Exits counted during the time bucket
in_csum
Cumulative entries since the daily reset (local midnight, per the query timezone)
out_csum
Cumulative exits since the daily reset
delta_sum
Net change during the bucket (in − out)
delta_csum
Cumulative net change since the daily reset
The cumulative fields are additive — in/out values and semantics are unchanged. Use in_csum at the end of a day for the day's total entries without summing buckets yourself.
Recommended Practices
Traffic Metrics: Use the
sumfunction to aggregate the total entries and exits over the defined period.Avoid Relative Time Queries: Do not use relative time functionality (e.g.,
-5m) as it may result in missing data depending on query timing. Always specify absolute start and stop times.Timezone Configuration: Always provide a timezone when querying traffic-based occupancy
Include Zero Values in Output: To ensure zero values are included in the results, add the filter:
Query the total hourly entrances and exits at a room or floor entrance.
Last updated