# Social Media Analytics API · Every Network (2026) · PostLake

> Markdown version of https://postlake.dev/guides/social-media-analytics-api . The canonical page for humans.
> PostLake is the social media API for AI agents: https://postlake.dev/llms.txt

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.

**In short:** GET /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](https://docs.postlake.dev/quickstart.md) uses. Do this once:

- Sign up at [app.postlake.dev](https://app.postlake.dev) and verify your email (unlocks free credits).
- 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.
- 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"
```

## Step by step

1. Use the same API key as publishing; accounts must already be connected.
1. Call `GET /v1/analytics?period=30d` (`7d` / `30d` / `90d`) for the roll-up.
1. Or `GET /v1/posts/{id}/analytics` for one publish across its targets.
1. Compare with identical field names, see [analytics docs](https://docs.postlake.dev/analytics) 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.

- Typical fields: impressions, reach, likes, comments, shares, saves, clicks, followers, see the [analytics docs](https://docs.postlake.dev/analytics) for the live schema.

- A network that does not expose a metric returns `0` or omits it. Your code can stay uniform either way.

- Per-post analytics covers every target that post published to, in one object.

## Do more with the numbers

- **Per-post**: `GET /v1/posts/{id}/analytics` for one publish across every network it hit.

- **Periods**: `7d`, `30d`, `90d` on the roll-up. Pick what your loop needs.

- **Feed an agent**: same field names everywhere, so “what worked?” is one comparison. Pair with [the agent guide](/guides/ai-social-media-agent).

- **No credit cost**: reading analytics is free. You pay only when something publishes.

## Pitfalls specific to this path

- Missing metrics are `0` or omitted. Don't treat omission as an API error.

- Fresh posts may lag while networks populate insights; empty early reads are normal.

- Analytics never costs credits; don't gate reads behind a publish budget check.

Building a feedback loop? Pair this with the [AI social agent](/guides/ai-social-media-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.](https://docs.postlake.dev/analytics)
    [Docs ### Publishing How posts get ids you can query analytics for.](https://docs.postlake.dev/publishing)
    [Docs ### MCP Analytics tools for agents over OAuth.](https://docs.postlake.dev/mcp)
    [Docs ### Quickstart Connect accounts before metrics appear.](https://docs.postlake.dev/quickstart)

## Related guides

- [Build an AI social agent](https://postlake.dev/guides/ai-social-media-agent.md)
- [Post everywhere at once](https://postlake.dev/guides/post-to-all-social-media-at-once.md)
- [Post with Python](https://postlake.dev/guides/python.md)
- [Post with LangChain](https://postlake.dev/guides/langchain.md)

[All guides](https://postlake.dev/guides/index.md) · [Full docs](https://docs.postlake.dev/) · [llms.txt](https://postlake.dev/llms.txt)

Plain markdown for agents: https://postlake.dev/guides/social-media-analytics-api.md · https://postlake.dev/llms.txt