Skip to main content

juicer.io/linkedin/api

LinkedIn Company Page posts, as JSON.

One key returns a Company Page's posts, hashtag results and Page profiles as the same normalized JSON as 14 other networks. No LinkedIn developer app, no partner program application, no token refresh.

curl "https://api.juicer.io/v1/data/posts?platforms=LinkedIn&term=yourcompany" -H "Authorization: Bearer $JUICER_API_KEY"

AI agents ready

Copy this prompt into the agent of your choice and get going right away.

I want to pull LinkedIn Company Page data through the Juicer API. Work from the official docs, not from memory.

1. Read https://developers.juicer.io first (or connect its docs MCP server, https://developers.juicer.io/mcp, no auth needed). The Quickstart and Authentication pages explain how to get going without a human signing up: POST /v1/authorize with an email returns a temporary API key, and a free Sandbox plan is available for a permanent one.
2. Then use the Juicer MCP server at https://api.juicer.io/mcp if you can, or the REST API at https://api.juicer.io/v1 with the key as a bearer token.
3. For LinkedIn: look up a Company Page's posts with platforms=LinkedIn and the Page's slug (the part after linkedin.com/company/), search a hashtag with term_type=hashtag, and resolve a Page's profile with the profiles lookup. Follow the docs for term types and cursor pagination.

Task: resolve the Company Page <yourcompany>, fetch its 10 latest posts and summarize the engagement.
  • Free Sandbox tier
  • No LinkedIn partner program
  • Cursor pagination
  • MCP server included

01 / posts

Pull a Company Page's posts.

Pass the Page's slug and get its recent posts: text, attached images or video, reaction and comment counts, posting time and the canonical URL. The same fields Instagram, Facebook and TikTok return, so one parser covers every network.

GET /data/posts in the docs →
GET /v1/data/posts?platforms=LinkedIn&term=yourcompany
{
  "data": [{
    "platform": "LinkedIn",
    "message": "We're hiring three engineers for the platform team. Remote, EU hours.",
    "poster": { "display_name": "Your Company" },
    "media": [{ "type": "image", "url": "https://..." }],
    "like_count": 412,
    "comment_count": 38,
    "url": "https://www.linkedin.com/feed/update/urn:li:activity:..."
  }],
  "meta": {
    "platforms": [{ "platform": "LinkedIn", "success": true, "has_more": true, "next_cursor": "..." }]
  }
}

GET /v1/data/posts 200 1 of 25 posts, 310 ms

Your Company

We're hiring three engineers for the platform team. Remote, EU hours.

412 38

02 / hashtags

Search public posts on a hashtag.

Pass a hashtag with term_type=hashtag and get recent public posts that use it, whoever published them: event coverage, employer-brand campaigns, industry conversation. Each post carries its author, so the JSON tells you who is talking.

term_type in the docs →
GET /v1/data/posts?platforms=LinkedIn&term=%23yourevent&term_type=hashtag
{
  "data": [
    { "platform": "LinkedIn", "poster": { "display_name": "Priya Nair" },
      "message": "Day one of #yourevent: the keynote on agent workflows was worth the trip alone.",
      "like_count": 96 },
    { "platform": "LinkedIn", "poster": { "display_name": "Marcus Dale" },
      "message": "Our booth at #yourevent is open until 6. Come talk procurement.",
      "like_count": 41 }
  ],
  "meta": { "platforms": [{ "platform": "LinkedIn", "success": true, "count": 2, "has_more": true }] }
}

GET /v1/data/posts 200 2 posts, 290 ms

  • Priya Nair

    Day one of #yourevent: the keynote on agent workflows was worth the trip alone.

  • Marcus Dale

    Our booth at #yourevent is open until 6. Come talk procurement.

03 / profiles

Resolve a Page to its profile.

Up to five handles per request. An exact handle match returns that Company Page with its follower count; otherwise you get candidates to disambiguate. Every profile carries every field, null where LinkedIn exposes nothing.

GET /data/profiles in the docs →
GET /v1/data/profiles?platforms=LinkedIn&term=yourcompany
{
  "data": [{
    "platform": "LinkedIn", "term": "yourcompany", "exact_match": true,
    "profiles": [{
      "handle": "yourcompany",
      "display_name": "Your Company",
      "url": "https://www.linkedin.com/company/yourcompany",
      "verified": null,
      "metrics": { "follower_count": 18460, "post_count": 1090, "total_view_count": null }
    }]
  }]
}

GET /v1/data/profiles 200 1 profile, exact match, 260 ms

Your Company

linkedin.com/company/yourcompany

Followers
18,460
Posts
1,090

04 / synced sources

Sync the Pages you follow. Get a webhook.

Add a Company Page, a profile, a hashtag or a group as a feed source and Juicer syncs it on a schedule, applies your moderation rules, keeps the history readable for free and calls your webhook when new posts land. LinkedIn sources sync asynchronously: the source is created at once and its first posts arrive a few minutes later, which the webhook announces.

Webhooks in the docs →
POST /v1/feeds/{feed_id}/sources
{ "platform": "LinkedIn", "term": "yourcompany", "term_type": "username" }

// later, on your endpoint
{
  "event": "post.created",
  "feed_id": 458361,
  "post": { "platform": "LinkedIn", "message": "New this week ...", "url": "https://..." }
}

POST /v1/feeds/458361/sources 201 source queued, syncing

post.created https://yourapp.com/hooks/juicer delivered 200

Use cases

What teams build on the LinkedIn API

The same normalized posts serve product features, marketing sites and AI workflows.

Company Page posts inside your product

Show a customer's LinkedIn activity in your CRM, sales intelligence tool or agency dashboard without a LinkedIn partnership of your own. Add their Page once and read it forever.

Employer-brand and careers pages

Pull the Company Page and the profiles of your people into a careers site or intranet, moderated, so candidates see real posts from real colleagues instead of stock photos.

Curated walls for conferences

Pull the hashtag behind an event and the Pages of its sponsors into one moderated stream and push the keepers to the venue screens, the event site or a print pipeline.

Monitoring and analytics

Archive posts and engagement counts for the Pages you track, yours and competitors', and chart follower counts, reactions and posting cadence over time.

LinkedIn data for AI agents

Give an agent get_data_posts and get_data_profiles through the MCP server and it can research a company, summarize what a prospect's Page has been saying or draft a reply with live context.

Retiring a hand-built scraper

Replace a brittle LinkedIn scraper, its proxies and its weekly selector fixes with one endpoint that Juicer keeps working. Most teams migrate in a day.

Why use Juicer instead of LinkedIn's API or a scraper?

LinkedIn's own API only serves the organizations you administer, after a partner program application and an app review, and offers no public search. Reading other Pages yourself means a scraper, proxies, layout changes and the ban risk that comes with them. Juicer carries all of it behind one normalized endpoint.

Build it yourself

A partner application, a scraper, and a pager.

  • Partner program application
  • Own Pages only, no public search
  • Scraper selectors breaking
  • Media URLs expiring
  • Rate limits and proxies
  • Moderation
  • Webhook plumbing
  • Engagement fields that move

Weeks to first post. Forever to maintain.

Juicer handles the heavy lifting.

With the Juicer API

One key. Same JSON as 14 other networks.

  • No LinkedIn developer app
  • Any public Company Page, not just yours
  • Hashtag search with authors
  • Page profiles with follower counts
  • Cached media that keeps working
  • Moderation applied before you read
  • Webhooks on new posts
  • MCP server for agents
Start with one API call

Questions

Frequently asked questions

What developers ask before pulling LinkedIn data through Juicer.

  • Do I need a LinkedIn developer app or partner program access?
    No. API lookups run against Juicer's own infrastructure: you pass a Company Page slug or a hashtag and get JSON back. There is no LinkedIn OAuth flow, no Marketing Developer Platform application and no app review on your side.
  • Which LinkedIn lookups are supported?
    On GET /data/posts, LinkedIn accepts term_type=username (a Company or School Page's posts, by the slug after linkedin.com/company/ or /school/) and term_type=hashtag (public posts on a hashtag). GET /data/profiles resolves Page handles to profiles with a follower count. Personal profiles, groups and mentions are feed source types: add them to a feed and read them through GET /feeds/{id}/posts.
  • Can I read personal profiles?
    As a feed source, yes: add a public profile by its linkedin.com/in URL and read its posts through the feed endpoints and webhooks. The connection-free /data/posts lookup covers Company Pages and hashtags; private profiles are never accessible.
  • How does pagination work?
    Each call returns one upstream page of results. meta.platforms[] carries has_more and an opaque next_cursor per platform; repeat the same request with cursor=<value> to continue. Cursors are per platform, so a multi-platform request paginates each network independently.
  • How current is the data?
    API lookups fetch fresh results at request time. Synced sources sync on the schedule you choose, from daily to every few minutes; LinkedIn syncs run asynchronously, so a new source reports its first posts a few minutes after creation. More frequent syncs spend credits proportionally faster, and reads of what has already been synced are free.
  • What does LinkedIn cost in credits?
    Reads of already-synced posts are free. A connected LinkedIn source costs 1 credit per sync; a premium (connection-free) LinkedIn source costs 3 credits per sync. Sandbox is free; Launch is $59 a month for 400 credits, Builder $99 for 750, Scale $499 for 4,500, Platform Partner from $2,500. The API pricing page has the calculator.
  • Is there an MCP server?
    Yes. Juicer's MCP server exposes the LinkedIn lookups as get_data_posts and get_data_profiles, next to feed, source, moderation, analytics and webhook tools, so an AI agent can pull LinkedIn content without custom scrapers or OAuth flows. It is available on every API plan, including the free Sandbox. The full reference lives at developers.juicer.io.
  • Can I display the posts instead of building a UI?
    Yes. The same account gives you the LinkedIn feed widget: add the Page, pick a layout and paste one embed code. Many teams use both, the widget for the marketing site and the API for the product.

Ready to build?

Start pulling LinkedIn data in minutes

A preview of a Juicer feed widget showing real social media posts