Analytics via API

Every network's numbers,
one shape.

Every network reports differently — different names, different units, different endpoints. PostLake maps them all to one metric shape, so "which post did best, and where?" is a single comparison instead of nine integrations and a translation layer.

Get started free →

No card for the free tier · one API for every network · full MCP access

The fastest way: ask your agent

Prefer no code at all? Connect PostLake's hosted MCP server to your AI assistant (Claude, ChatGPT, Cursor and others) and just ask it to post. It authorizes over OAuth — no key to paste. See the MCP guide.

Read every network at once

One call rolls up performance across every connected account:

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

# Or for one post, across everywhere it went
curl https://api.postlake.dev/v1/posts/post_a1b2c3/analytics \
  -H "Authorization: Bearer YOUR_API_KEY"

Step by step

Create a PostLake API key (Settings → API Keys) and connect the accounts you want measured.
Call GET /v1/analytics?period=30d for a cross-platform roll-up — use 7d, 30d or 90d.
Or call GET /v1/posts/{id}/analytics for one post's numbers across every network it published to.
Read the same field names everywhere: impressions, reach, likes, comments, shares, saves, clicks, followers.

Good to know

Not every network exposes every metric — the missing ones come back as 0 or omitted, so your handling stays uniform either way.
Because the shape is normalised, an AI agent can ask "what should I post next?" and reason over one consistent response.
Reading analytics doesn't cost credits — you pay per post, not per query.
Full field reference is in the analytics docs.

Why PostLake

One call, every network

List the platforms in one request and PostLake posts to all of them, returning a single normalised shape — your code never branches per platform.

No app setup

PostLake manages each network's developer app and OAuth for you — nothing to register or get reviewed yourself.

Agent-safe

Idempotency keys mean a retry never double-posts, and analytics come back normalised so an agent can decide what to post next.

Honest pricing

A free tier to start, then usage-based credits — one per post. You only pay for posts that actually publish.

Common questions

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

Yes — PostLake's GET /v1/analytics returns performance across every connected account in one call, with the same metric names for every network so you don't write a translation layer per platform.

What metrics does the analytics API return?

Impressions, reach, likes, comments, shares, saves, clicks and follower count, under identical field names on every network. Metrics a given network doesn't expose come back as 0 or are omitted.

Can I get analytics for a single post?

Yes — GET /v1/posts/{id}/analytics returns that post's numbers across every network it was published to, in the same normalised shape.

Do analytics calls cost credits?

No. Credits are spent on publishing, not on reading analytics.

More guides

Python · Node.js · n8n · Make · Zapier · All guides · Full docs

One API and MCP server for every major network. Free to start.