Analytics

Post Analytics

Get per-platform analytics for a specific post. Only available for posts with status posted or partial. It lists the post's accounts that are in the workspace now; a post none of whose accounts are in the workspace any more answers 404 NOT_FOUND there.

Example Request

curl https://api.quegly.com/v1/analytics/post/post-abc123 \
  -H "Authorization: qgl_your_api_key"

Response

{
  "post_id": "post-abc123",
  "platforms": [
    {
      "platform": "instagram",
      "account_id": "acc-instagram-123",
      "post_url": "https://www.instagram.com/p/abc123",
      "metrics": {
        "views": 15420,
        "reach": 11290,
        "likes": 892,
        "comments": 47,
        "shares": 123,
        "saved": 234,
        "total_interactions": 1296
      },
      "fetched_at": "2026-06-02T10:00:00.000Z"
    },
    {
      "platform": "x",
      "account_id": "acc-x-345",
      "post_url": "https://x.com/user/status/123456",
      "metrics": {
        "views": 38400,
        "impressions": 38400,
        "likes": 412,
        "comments": 18,
        "retweets": 67,
        "quotes": 9,
        "bookmarks": 51,
        "url_link_clicks": 124,
        "user_profile_clicks": 22
      },
      "fetched_at": "2026-06-02T10:00:00.000Z"
    }
  ]
}

The metrics object is platform- specific. Keys vary by platform (TikTok exposes 4 keys, YouTube up to 10). See the table below for what each platform actually returns. Missing keys mean "the platform didn't expose that metric for this post," never zero.

Workspace Analytics (bulk)

Every published post in a date window with its per-platform metrics, in one call. Serves cached snapshots only; never hits platform APIs. Pair with the refresh endpoint below when freshness matters.

Example Request

curl "https://api.quegly.com/v1/analytics?start_date=2026-06-01&end_date=2026-06-30" \
  -H "Authorization: qgl_your_api_key"

Response

{
  "workspace_id": "ws-123",
  "start_date": "2026-06-01T00:00:00.000Z",
  "end_date": "2026-06-30T23:59:59.000Z",
  "count": 1,
  "posts": [
    {
      "id": "post-abc123",
      "caption": "3 Ways to Prep Your Skin Before a Big Event",
      "status": "posted",
      "scheduled_at": "2026-06-28T13:00:00.000Z",
      "platforms": [
        {
          "platform": "instagram",
          "account_username": "myhandle",
          "post_url": "https://www.instagram.com/p/abc123",
          "metrics": { "views": 15420, "likes": 892, "comments": 47 },
          "captured_at": "2026-06-29T10:00:00.000Z"
        }
      ]
    }
  ]
}

metrics is empty and captured_at is null when nothing has been captured yet for that post+platform (distinct from a captured 0). The window may reach back past 30 days; posts older than the refresh window return their last (frozen) snapshot.

Refresh Analytics

Trigger an on-demand refresh sweep for the workspace. The scripted flow is: refresh, wait a few seconds, then GET /v1/analytics. Repeat calls within an hour re-fetch nothing, and posts older than 30 days are never re-fetched by any path.

Example Request

curl -X POST https://api.quegly.com/v1/analytics/refresh \
  -H "Authorization: qgl_your_api_key"

Response

{
  "workspace_id": "ws-123",
  "attempted": 42,
  "refreshed": 40,
  "skipped": 108,
  "failed": 2
}

attempted = stale rows fetched this sweep; refreshed = fetched and stored; skipped = still fresh inside the 1-hour on-demand TTL (or LinkedIn's or Pinterest's slower cadence); failed = platform errors, picked up again on a later sweep.

Available Metrics by Platform

What we actually pull from each platform's analytics API. Keys map 1:1 to the metrics object in the response.

Analytics are served from a database cache, refreshed on a read-through pattern when the dashboard's Analytics page is opened or when you call POST /v1/analytics/refresh. Hitting the read endpoints repeatedly is cheap and won't cost extra platform-side reads.

For scripted pulls: POST /v1/analytics/refresh, wait a few seconds, then GET /v1/analytics. Calling refresh more than once an hour is a no-op, so there's no way to overspend platform reads by accident.

Five real cases worth knowing about before you call this endpoint in production. Each one will show up as "empty metrics" or "missing fields" and is otherwise hard to debug from the response alone.