Guides
Analytics
Read how your posts performed — per post, or across every network at once — in one normalised response. Same metric names everywhere, so you (or an agent) can compare platforms without special-casing each one.
Per-post analytics
Fetch the metrics for a single post across all the accounts it went to:
curl https://api.postlake.dev/v1/posts/post_a1b2c3/analytics \
-H "Authorization: Bearer YOUR_API_KEY"Cross-platform analytics
Roll up performance across every connected account over a period (this is the differentiator — one call, every network):
curl "https://api.postlake.dev/v1/analytics?period=30d" \
-H "Authorization: Bearer YOUR_API_KEY"Use period to set the window (e.g. 7d, 30d, 90d).
The metric shape
Every platform maps to the same Metrics object, so a chart or an agent reads one set of fields regardless of source:
| Field | Meaning |
|---|---|
impressions | Times the post was shown. |
reach | Unique accounts that saw it. |
likes | Likes / reactions. |
comments | Comments / replies. |
shares | Reposts / shares. |
saves | Saves / bookmarks. |
clicks | Link / profile clicks. |
followers | Follower count / growth for the account. |
Not every network exposes every metric; unavailable ones come back as 0 or omitted, so your handling stays uniform.
Why an agent cares. Because the response is normalised, an assistant can ask "which of last week's posts did best, and on which network?" and reason over one consistent shape — then decide what to post next.