One user's active time, memory totals and current device.

Use the existing organization bearer token and discover user IDs with GET /api/v1/users. Unknown and inaccessible users both return 404. Scoped dashboard logins receive 403. Limited to 120 requests per minute.

Dates are inclusive Asia/Kolkata calendar dates within the last 7 days; omit both for today. With start_date only, the range ends today. With end_date only, the range covers that single day. Longer ranges return 400.

Active time merges connected presence and recordings within each day's window: the whole IST day (00:00-24:00) unless your organization has a different window configured. The window is reported as workday_start and workday_end, and per day as window_start and window_end. active_time.days lists each date with its total and its activity intervals: when the device was connected or recording, including time connected without recording, merged so nothing is counted twice and clipped to the day's window. A day's interval durations sum to its device_active_seconds.

Reconstruction needs about 25 hours of history before the day starts: today minus 6 is always incomplete, and today minus 5 becomes incomplete around 23:00 IST. Missing source days make the range total null with state: incomplete and are listed in missing_dates; those days have null totals and null intervals, while the other days are still reported. Zero is a reconstructed zero. Values are telemetry-based estimates.

Memory totals filter created_at, exclude archived/deleted memories and count positive recording duration. Sales duration uses the domains array. Device status and battery describe the current primary device even for historical requests. Battery and device can be null. Source outages return 503 rather than fabricated zeros; battery lookup failure only clears battery.

Poll per user, spread requests across the hour and use bounded concurrency. This endpoint performs no domain writes and does not add authentication scopes or credentials.