logoPandorLabs
LinkedIn logoThe professional graph

LinkedIn Data, Delivered

Public LinkedIn content and engagement metrics, normalised to the same schema as every other platform we cover and pushed into your stack. Nothing to build, nothing to maintain.

source specification

Source
LinkedIn logolinkedin.com
Objects
Company pages, Public posts, Job postings, Public profiles, Engagement metrics
Formats
JSON · CSV · Parquet
Refresh
Continuous to daily
Scope
Public content only

about the platform

What makes LinkedIn different

LinkedIn is the only social network where the graph is professional rather than personal, which makes its public surface structurally different from every other platform. Company pages, job postings, and public posts describe organisations rather than individuals — headcount direction, which functions a company is investing in, which markets it is opening, and how its executives are positioning it publicly. That is business intelligence that happens to be published as social content.

why teams track it

Why LinkedIn data is worth having

For B2B teams, LinkedIn is the highest-signal public data source that exists: hiring patterns lead revenue, executive posts lead announcements, and company page changes lead strategy shifts. Sales teams use it for account-level trigger events, competitive intelligence teams use job postings as a leading indicator of product direction, and recruiters use it to map talent markets that no other source describes.

Visit linkedin.com

pricing

Pay per profile delivered

Every LinkedIn lookup is billed in credits, per profile we actually return, at $0.06, down to $0.015 in volume a credit. Pick cached or live on each request. Anything we cannot deliver is refunded automatically.

Cached

1credit / profile

$0.06, down to $0.015 in volume per profile

Answered from the profiles we already hold, or from the enrichment index when we do not. Instant, and the cheapest way to fill a list.

  • Served straight from the stored dataset when the profile is already there
  • Falls back to the index for anything missing
  • Best for enrichment, CRM backfill and bulk lists

Live

2credits / profile

$0.12, down to $0.03 in volume per profile

Scraped from the source at request time, so every field is as current as the profile itself.

  • Fetched fresh on every request, never from a cache
  • Every field as it reads on the source right now
  • Best for change alerts and outreach triggers
  • Invalid, missing and failed profiles cost nothing
  • Interrupted requests are refunded in full, automatically
  • Duplicates in a batch are billed once
  • Up to 10 profiles per request
  • Credit packs from $300, paid once through Stripe
  • Cached vs live usage tracked in your dashboard
Terminal
curl -X POST \  https://api.pandorlabs.com/v1/lookups/linkedin \  -H "Authorization: Bearer $PANDORLABS_KEY" \  -H "content-type: application/json" \  -d '{    "targets": ["https://www.linkedin.com/…"],    "freshness": "cached"  }'

applications

What teams build on LinkedIn data

Hiring signals as a growth indicator

Job posting volume by function is one of the earliest public signals a company gives about where it is investing. A sudden run of enterprise sales roles reads differently from a run of research roles, and both precede any announcement.

Account-level trigger events

New leadership, a new office, a funding announcement, or a hiring surge each mark an account as newly in-market. Feeding those triggers into your CRM is the difference between outbound that lands and outbound that annoys.

Competitive product direction

What a competitor hires for describes what it is building, months before anything ships. Engineering role titles and required skills are a surprisingly literal roadmap.

Talent market mapping

Aggregate public profile and posting data describes where a skill set is concentrated, what it is being paid, and which companies are gaining or losing people in it.

Executive share-of-voice

Track how often your leadership and your competitors post, on which themes, and how much engagement each generates — the B2B equivalent of brand share-of-voice tracking.

ICP and firmographic enrichment

Company page attributes enrich an account list with industry, size, and geography, so segmentation runs on current data rather than whatever was true when the list was bought.

what you get back

Fields in the LinkedIn feed

Platform-specific detail on top of the unified social schema, so a dashboard built on one platform works on the next without a rewrite.

  • Company page attributes — industry, size band, headquarters, specialties
  • Job postings with title, function, seniority, and location
  • Public post content with author, timestamp, and engagement envelope
  • Reaction, comment, and repost counts per post
  • Public profile fields where the member has made them visible

Public surfaces only

We collect what a logged-out visitor can see. No authentication is bypassed, no private content is touched, and no attempt is made to deanonymise anyone.

One schema across platforms

A post from any network arrives with the same field names, so adding a platform does not mean rewriting anything downstream.

Deletion propagates

When content is removed at source it drops out of subsequent deliveries, and retention windows on delivered data are configurable per engagement.

Data
Browse Collected Rows
API
Programmatic Access
Files
JSON and CSV
Runs
Track Extraction Progress

questions

Frequently Asked Questions

Everything you need to know before you send us your first request.

What LinkedIn data do you collect, exactly?
Public surfaces only: company pages, public job postings, public posts and their engagement counts, and profile fields a member has chosen to make publicly visible. We do not access content behind a login, we do not touch private profiles, connections, or messages, and we do not attempt to infer anything a member has not published. During scoping we confirm in writing exactly which fields you can rely on, because the public surface is narrower than most people assume.
Is collecting LinkedIn data legal?
We collect only publicly available pages — the surface a logged-out visitor can see — and we do not circumvent authentication or access controls. Because professional data can constitute personal data under GDPR, we treat it as such: data is stored in your chosen region, retention windows are configurable, deletion propagates through the pipeline when content is removed at source, and our DPA is available before you sign. We will not build a use case that depends on deanonymising individuals.
Can you track a specific list of companies?
Yes, and this is the most common configuration. You supply an account list — by company page, domain, or name — and we monitor those organisations continuously, pushing job postings, page changes, and public posts as they appear. Most customers wire this straight into their CRM as trigger events rather than consuming it as a dataset.
How fresh is the LinkedIn data?
Cadence is yours to set. Account monitoring for trigger events typically runs daily, which is fast enough that a job posting reaches your CRM within a day of going live. Broader market mapping usually runs weekly, since the aggregate picture does not move fast enough to justify more.
How is LinkedIn data delivered?
Browse collected rows in the dashboard, export datasets as JSON or CSV, or query them through the API and MCP server. Contact us to discuss other delivery requirements.
What happens when linkedin.com changes?
Keeping the collector working is our responsibility. Extractors are monitored continuously, and when the platform changes its structure we patch upstream while the schema we deliver to you stays fixed. If a change causes a coverage gap we tell you which window was affected rather than quietly returning fewer records.
How does pricing work for LinkedIn lookups?
On-demand lookups are billed in credits per profile delivered: 1 credit for a cached result and 2 credits for a live one scraped at request time. A credit costs $0.06, down to $0.015 in volume, bought in one-time packs. Credits are reserved when the request starts and refunded for any profile that turns out invalid, missing or unreachable, so you only pay for data you receive. Continuous feeds into your warehouse are still scoped per engagement.

Still have questions?

Talk to an engineer

Ready to Get Started?

Talk to us about your sources and volume. We'll return a sample dataset from your target sites before you commit to anything.

Scoped API Access
Discuss Data Requirements
Run tracking

© 2026 PandorLabs LLC. All rights reserved.