Read analytics - Postinger

Analytics requires analytics-read. Read analytics capabilities first to discover enabled platforms and metric names.

postinger analytics capabilities
postinger analytics report --from 2026-09-01 --to 2026-09-30 --json
postinger analytics account ACCOUNT_ID --from 2026-09-01 --to 2026-09-30 --json
postinger analytics posts --days 30 --limit 25 --json

Choose a range

Account and report dates are inclusive UTC dates, provided as both from and to, covering at most 366 days. Post analytics accepts days of 7, 30, or 90 (default 30), or a paired from/to range. Date filters on post analytics select publication time, not when engagement happened.

Interpret measurements

Counters are decimal strings. Preserve them if your language cannot safely represent large integers.
null means missing data, not zero.
Metric status can be available, unavailable, unsupported, or permission_required.
collectedAt is the measurement time. generatedAt is the response generation time.
Check report partial, comparisonReason, and freshness coverage before comparing periods.

Account counters are the latest stored totals, even when a historical date range is selected. Daily activity metrics use the requested range. The followers chart represents daily changes; its headline value is the last observed total.

Post history

postinger analytics history POST_ID ACCOUNT_ID --json

History returns up to the latest 1,000 retained observations, ordered oldest first. Recent 30-day history uses raw observations; older retained data uses daily closing observations. Counters are cumulative, not interval deltas. All analytics calls read stored measurements. They do not trigger collection. See pagination for larger result sets.