A LinkedIn API you can actually get

The wall, and when you hit it

The usual sequence goes like this. You read the developer docs, find that sign-in works immediately, and conclude the rest will be similar. You build. Then you reach for post analytics, or for publishing on a member's behalf, and discover that the endpoint you need belongs to a partner program with an application form and no published review time.

This is not a complaint about LinkedIn — gating write access to a social graph is a defensible choice, and the alternative is the spam-filled API surface some other networks used to have. But it does mean that “we'll just use the LinkedIn API” is a plan with an unbounded unknown in it, and it is better to find that out before the sprint than during it.

Three honest options

Including the one where you do not use us.

Same capabilities, three surfaces

Nothing exists in only one of them, so pick by what you are building rather than by what you are allowed.

HTTP, for your own backend

curl -X POST https://studio.blabigo.ai/api/mcp/linkedin \
  -H "Authorization: Bearer mcp_live_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

CLI, for scripts and CI

npm install -g @blabigo/cli
blabigo auth login --key mcp_live_your_key_here

blabigo posts create --account wla_123 \
  --at 2026-10-01T09:00:00Z \
  --text "Shipping something new today."

posts create requires either --at or --draft. There is no default, because ambiguity should never end with something appearing on a real feed.

MCP, for AI agents

The same operations as 13 tools an assistant can call directly. See the tool list →

Frequently asked questions

Is there a LinkedIn API alternative for posting and analytics?

Not an unofficial one worth using — LinkedIn is the only source of LinkedIn data, and anything claiming otherwise is scraping. The practical alternative is to build on a platform that already holds partner access and exposes it to you. Blabigo does that through a REST API, a CLI and an MCP server, so your integration ships without waiting on an approval queue.

Why is LinkedIn's API so hard to get access to?

The capabilities most developers want — publishing on a member's behalf, reading post-level analytics, managing company Pages — sit behind partner programs that LinkedIn reviews case by case. The self-serve products cover sign-in and narrow sharing cases. There is no published timeline for review, which is what makes it hard to plan around rather than merely hard.

Can I get LinkedIn post analytics without partner access?

Not through LinkedIn directly. Impressions, clicks and engagement per post come from gated endpoints. Through Blabigo you can read them for your own connected accounts via the API, the CLI or the MCP tools, because Blabigo holds the access and is acting on your behalf.

Is scraping LinkedIn a viable option?

No. It breaches LinkedIn's terms of service, exposes the account doing it to restriction, and breaks without warning whenever the page markup changes. It is also a poor foundation for anything you intend to sell, since your product's reliability depends on a site that has every reason to stop you.

What does Blabigo's API actually let me do?

List connected accounts and Pages, read post and account analytics, refresh metrics from LinkedIn, list and read posts, create and edit drafts, queue posts for a future time, reschedule, cancel and archive. What it does not let you do is publish immediately or delete — those limits apply to every route equally, including the ones you call from your own code.

Do I have to use MCP, or can I call plain HTTP?

Either. The same capabilities are available as JSON-RPC over HTTP for MCP clients, as a CLI for scripts and CI, and as ordinary authenticated HTTP requests. Use whichever matches what you are building; there is no feature that exists in only one of them.