Analytics via API

Every network's numbers,
one shape.

Networks disagree on metric names and endpoints. PostLake maps them to one shape so "which post did best, and where?" is one comparison. The differentiator called out in the product docs.

Get started free →

Free tier. No card · one API for every network · full MCP access

In shortGET /v1/analytics (or per-post analytics) returns the same metric names on every network, compare without a translation layer. Free to read.

When this guide is for you

You need cross-network performance in a dashboard, report, or agent feedback loop.

Before you start

Same setup the docs quickstart uses. Do this once:

  1. Sign up at app.postlake.dev and verify your email (unlocks free credits).
  2. On Channels, create a profile (e.g. my-brand) and connect at least one account. Bluesky is the fastest first channel: no app review. Instagram/TikTok/Facebook need each platform's review before API posting.
  3. Account menu → API Keys → create a key (sk_live_…). It shows once; treat it like a password.

Roll-up or one post

Same auth as publishing. Reading analytics does not spend credits:

# Across connected accounts
curl "https://api.postlake.dev/v1/analytics?period=30d" \
  -H "Authorization: Bearer YOUR_API_KEY"

# One post. Every network it hit
curl https://api.postlake.dev/v1/posts/post_a1b2c3/analytics \
  -H "Authorization: Bearer YOUR_API_KEY"

Make it work

Tool-specific glue on top of the shared setup above:

  1. Use the same API key as publishing; accounts must already be connected.
  2. Call GET /v1/analytics?period=30d (7d / 30d / 90d) for the roll-up.
  3. Or GET /v1/posts/{id}/analytics for one publish across its targets.
  4. Compare with identical field names, see analytics docs for the schema.

Read the response

Roll-up and per-post analytics use the same metric names on every network, that is the point. Compare platforms without a translation layer.

Do more with the numbers

Pitfalls specific to this path

Building a feedback loop? Pair this with the AI social agent guide or MCP analytics tools.

Common questions

Is there one API for social media analytics across all networks?

Yes. GET /v1/analytics returns performance across connected accounts with the same metric names per network. Full field reference: docs → Analytics.

What metrics does it return?

Impressions, reach, likes, comments, shares, saves, clicks, followers, under identical names. Networks that lack a metric return 0 or omit it.

Can I get analytics for a single post?

Yes. GET /v1/posts/{id}/analytics returns that post across every network it published to.

Do analytics calls cost credits?

No. Credits are for publishing. Reads are free.

Go deeper in the docs

Canonical metric schema and examples:

Docs

Analytics

Roll-ups, per-post metrics, field reference.

 Docs

Publishing

How posts get ids you can query analytics for.

 Docs

MCP

Analytics tools for agents over OAuth.

 Docs

Quickstart

Connect accounts before metrics appear.

Related guides

AI agents

Build an AI social agent

Build an agent that writes, posts and learns on its own.

 Topics

Post everywhere at once

Cross-post everywhere with a single request.

 From code

Post with Python

Post to every network from a few lines of Python.

 AI agents

Post with LangChain

Give your LangChain agent the power to post.

All guides · Full docs · llms.txt · Markdown

Stuck? The docs are the source of truth, start at Analytics.

Open the dashboard →