Analytics

Get analytics overview

Changed on

Totals for the workspace of this API key over a period (period, default 30 days, or start_date and end_date), with a breakdown per platform. Requires the analytics:read scope.

get/analytics/overview

Request

  • Base URL
    https://api.omnisocials.com/v1
  • URL
    https://api.omnisocials.com/v1/analytics/overview
  • Auth
    HTTP bearer

Query parameters

period'7d' | '30d' | '90d'

Time period for analytics

start_datestring
Example:2026-09-01

Custom start date. Accepts YYYY-MM-DD (e.g. "2026-04-01"), YYYY-MM month-shorthand (e.g. "2026-04" expands to the first of the month), or a full ISO 8601 datetime.

end_datestring
Example:2026-09-30

Custom end date. Same formats as start_date; "YYYY-MM" expands to the last day of the month.

tagstring
Example:Question hook

Post numbers of the posts with this tag only: a tag id or name, comma separated for any of several. Account numbers (followers, account reach) stay those of the whole account. An unknown tag answers 404 tag_not_found.

Response

Analytics overview

periodstring

Human-readable range label (e.g. "30d" or "2026-04-01 to 2026-04-30")

start_datestring date

Resolved range start (YYYY-MM-DD), useful for clients that want to confirm what was queried

end_datestring date

Resolved range end (YYYY-MM-DD)

current_datestring date

Server's current date (UTC), included so clients can self-correct relative phrases like "last month"

Example response

{
  "data": {
    "total_posts": 42,
    "total_platforms": 4,
    "total_engagement": 3180,
    "total_impressions": 96400,
    "average_engagement_rate": 3.3,
    "top_performing_platform": "instagram"
  },
  "period": "30d",
  "start_date": "2026-09-21",
  "end_date": "2026-10-21",
  "current_date": "2026-10-21"
}

Changes