PostEverywhere Analytics Summary Reference
Aggregate counters and per-platform totals for the current workspace, in one call instead of listing every post.
Returns aggregate counts for a time window. Answers questions like "how many posts have I published this month?" or "which platform has the most failures this week?" without listing every post and counting client-side.
Pull performance totals across accounts: GET /v1/analytics/summary
curl "https://app.posteverywhere.ai/api/v1/analytics/summary?period=week" \
-H "Authorization: Bearer $POSTEVERYWHERE_API_KEY"
Filtering the summary by date, account and platform
| Param | Values | Default |
|---|---|---|
period |
today (24 h), week (7 d), month (30 d), all, custom |
month |
from |
ISO timestamp (required if period=custom) |
N/A |
to |
ISO timestamp (required if period=custom) |
N/A |
What the analytics response returns
{
"data": {
"period": "week",
"range": { "from": "2026-06-04T05:30:00Z", "to": "2026-06-11T05:30:00Z" },
"posts": {
"total": 214,
"draft": 3,
"scheduled": 168,
"publishing": 2,
"published": 33,
"partially_failed": 4,
"failed": 4
},
"by_platform": [
{ "platform": "instagram", "total": 67, "scheduled": 55, "published": 11, "failed": 1 },
{ "platform": "tiktok", "total": 41, "scheduled": 38, "published": 0, "failed": 3 },
{ "platform": "linkedin", "total": 38, "scheduled": 30, "published": 8, "failed": 0 }
],
"metrics": {
"views": 12483,
"likes": 872,
"comments": 143,
"shares": 29,
"impressions": 41208,
"clicks": 518
},
"ai_credits": {
"used_this_period": 138,
"bonus": 0
}
},
"error": null,
"meta": { "request_id": "a1b2c3d4", "timestamp": "2026-06-11T09:55:12.341Z" }
}
Which metrics each platform actually reports
posts.totalcounts unique post groups. Multi-platform posts count as one here, not one per destination.by_platform.totalcounts destinations, so a 5-platform post contributes 5 rows total.metricsaggregates only thepublisheddestinations. Failed destinations don't have metrics.- Status counts use the derived post status, the same as
GET /v1/posts's status filter (scheduled/publishing/published/partially_failed/failed/draft).
How PostEverywhere derives a post's status
Post status is derived live from the destinations underneath it. Note the vocabulary
shift: a destination that published successfully is done, never published.
See the two status vocabularies.
published: every destination isdonefailed: at least 1 destinationfailed, nonedone, none queuedpartially_failed: at least 1 destinationdoneAND at least 1failedpublishing: at least 1 destination is in flight (preparing/uploading/publishing/verifying)scheduled: at least 1 destinationqueuedand nothing published yetdraft:posts.post_status = 'draft'
Metric availability, platform by platform
The metrics block is only as complete as what each platform's API gives us back, and
that varies a lot. Read this before building a dashboard on it, so a zero reads as
"this platform does not report it" rather than "this post got nothing".
| Platform | Views | Likes | Comments | Shares | Impressions | Notes |
|---|---|---|---|---|---|---|
| YouTube | yes | yes | yes | - | - | Most complete source |
| TikTok | yes | yes | yes | yes | - | Live since Jul 28 2026. Accounts connected before Jul 3 2026 must reconnect once to grant the analytics scope |
| yes | yes | - | yes | yes | Saves are counted as likes, outbound clicks as shares, impressions as views | |
| - | yes | yes | yes | yes | Company-page posts only (needs the organization admin scope); personal-profile posts return no metrics; no view count | |
| - | yes | yes | - | - | Insights pending Meta App Review | |
| X | - | yes | yes | yes | yes | Refreshed on demand only (each read costs API credits), press Refresh on the analytics page |
| Bluesky | - | yes | yes | yes | - | Replies as comments, reposts as shares |
| - | - | - | - | - | Blocked on pages_read_engagement Advanced Access, pending Meta App Review |
|
| Threads | - | - | - | - | - | Blocked on threads_manage_insights, pending Meta App Review |
| Telegram, Discord, WordPress | - | - | - | - | - | No per-post analytics available for these integrations (WordPress core has no stats API) |
A field we do not receive is returned as 0 in the aggregate and null on the
individual destination, so null is the honest signal for "not reported".
Reach and follower growth are not available
The API exposes no reach metric and no follower counts or follower growth, on any platform.
impressionsis the closest available measure and is not the same thing. If you need either, tell us at support@posteverywhere.ai so we can weight the work.
Related: per-account health · listing individual posts · filtering by campaign · analytics coverage changes
Full reference: GET /v1/analytics/summary.