LinkedIn post scraper for company pages - bulk-export posts with engagement, hashtags, mentions, and author profile enrichment (headline, industry, location, followers). Filter by keyword; sort by top engagement. Paste URLs or bare handles like 'google'. No login, no cookies. >99% success.
Removed - absolute date range inputs (posted_after_date, posted_before_date)
Diagnostic testing on 2026-10-06 confirmed that HarvestAPI's LinkedIn
endpoints only return roughly the last ~12 months of posts per company
or profile. This limit holds across both /linkedin/company-posts
(tested with Rogers Machinery: 265 posts spanning only 2025-10-06 to
2026-10-05) and /linkedin/profile-posts (tested with Reid Hoffman,
LinkedIn's co-founder posting since 2010: 149 posts spanning only
2025-11-06 to 2026-09-30). It's a structural constraint of cookieless
LinkedIn scraping, not a bug in this Actor.
Keeping absolute-date inputs in the form led users to specify historical
windows that silently returned zero results for every URL. The two
inputs were already hidden from the schema in v1.4.4; v1.4.9 removes
them from code entirely.
What was removed
input.posted_after_date and input.posted_before_date are no
longer read.
Their validation (bad format, after > before) is gone.
The client-side date filter in the per-page batch filter is gone.
The postedLimitDate / postedBeforeDate params to HarvestAPI's
/linkedin/company-posts call are gone (they were pass-through but
the endpoint doesn't deeply honor them anyway).
getPostedDate and normalizeIsoDate helpers are now unused and
removed.
buildEmptyReason (from v1.4.8) no longer takes the two absolute
dates; its branches that referenced them are gone.
Legacy input compatibility
A saved Task or API call that still carries posted_after_date or
posted_before_date in its input no longer errors. The Actor logs a
one-line warning naming the removed field and ignores it, then runs
with the other inputs as given. No run crashes.
Of the 10 refreshed Tasks and the 4 bootstrap recipes, none used
absolute dates (they all use date_filter), so this change is a
no-op for every Task on this Actor's current list.
What still works for date filtering
date_filter (the rolling "Posted within" dropdown) is unchanged.
Options: last hour, 24 hours, week, month, 3 months, 6 months, year.
All work because they stay within the ~12-month HarvestAPI buffer.
content_contains (keyword filter) is unchanged.
Pricing / schema
Zero pricing event change. Zero output column change. Only the two
removed input fields are gone (they were already hidden in v1.4.4).
[1.4.8] - 2026-10-06
Changed - empty-row placeholders now carry a human-readable reason
Previously an empty row (company page returned no in-filter posts)
was a wall of nulls across every column in the dataset preview. Users
had to open the per-URL log to understand WHY a row was empty.
The content field on empty placeholder rows now carries a short
context-aware explanation so the dataset preview is self-explaining.
Error rows are unchanged (they still carry the structured error
object as before).
Message shape (filled into content on empty rows only)
Date range set, zero in-range posts:
"No posts between 2024-09-23 and 2025-09-07. Company posted N+ time(s) outside this window."
Rolling filter set (date_filter), zero in-range posts:
"No posts in the last month. Company has N+ older post(s)."
include_reposts=false and all were reposts:
"All N post(s) were reposts (filtered out by include_reposts=false)."
include_quote_posts=false and all were quote posts:
"All N post(s) were quote posts (filtered out by include_quote_posts=false)."
content_contains set, nothing matched:
"None of the N post(s) found contained the required keyword(s): ..."
No filters, truly empty company page:
"No posts found on this company page."
No in-filter posts and no raw posts either:
"No posts found on this company page to check against your filters."
Compatibility
Zero schema change (reuses the existing content field).
Zero pricing event change.
Rows that have real post content behave identically to before
(content is still the post body).
Downstream consumers that filter by post_url !== null to
distinguish real posts from placeholders continue to work.
[1.4.7] - 2026-10-06
Fixed - pagination stopped early when client-side filter dropped a page
Critical bug exposed by date-range runs. The company-posts page loop
broke when batch.length === 0 (post-filter), but a non-empty raw
HarvestAPI page can filter down to zero rows when the client-side
filters (posted_after_date, posted_before_date, content_contains,
include_quote_posts: false, include_reposts: false) drop every
row returned.
Real impact for date-range runs: HarvestAPI returns posts newest-
first. For any company that posts actively (small businesses that
posted in the last 13 months), page 1 is dominated by posts newer
than a posted_before_date cutoff. All 50 fail the client filter,
batch.length === 0, the loop breaks, and the Actor never checks
page 2 where older posts in the user's window would be. Result:
"0 rows delivered" for every active company in a backward-looking
date range run, even though the data was reachable.
Change
Loop now breaks on rawBatch.length === 0 (HarvestAPI genuinely
exhausted) instead of batch.length === 0 (local filter emptied
the batch). Pagination continues until HarvestAPI has nothing more,
or max_posts is reached, or the 50-page ceiling is hit.
No change for runs without aggressive client-side filtering: when
no filter drops rows, rawBatch.length === batch.length and the
break fires at the same point as before.
Zero schema change. Zero pricing event change. Zero output column
change. Behavior change is a strict improvement: date-filtered runs
now reach data they used to silently skip. Non-filtered runs behave
identically to before.
Cost impact
Marginal. Backward-looking date-range runs will now fetch more pages
per active URL (previously bailed after 1 page). For a typical 2000-URL
run with a 1-year window:
Before fix: ~2000 pages × $0.0023 = ~$4.60, almost no rows delivered
After fix: ~2000 URLs × avg 3-5 pages × $0.0023 = ~$14-$23, full
window delivered
Expected revenue goes up roughly in proportion to delivered rows.
[1.4.6] - 2026-10-05
Changed - repost diagnostic uses log.info
The repost-structure diagnostic added in v1.4.5 used console.log,
which some Apify log views filter out. Switched to log.info so the
line reliably shows in the main run log view.
Also extended the snippet length from 300 to 500 chars so more of
HarvestAPI's actual nested structure fits on one line.
Zero behavior change beyond log visibility.
[1.4.5] - 2026-10-05
Fixed - reposted_by_name null on actual reposts
The reposted_by_name output column read HarvestAPI's documented
repostedBy.name field but was coming back null on every repost
row. Added fallback paths that check raw.repost.author.name,
raw.repost.actor.name, and raw.repost.by.name in order. First
non-empty wins.
Added a one-shot diagnostic log line when a repost arrives with no
resolvable name on any of the known paths, dumping the raw
repostId, repostedBy, and repost structures so we can see
HarvestAPI's actual field layout and extend the fallbacks in a
future patch.
Backwards compatibility
Zero schema change. Every output column name, order, and type is
identical.
Zero pricing event change. The 7 billing events fire identically.
Non-repost rows (is_repost: false) always had
reposted_by_name: null and still do.
Repost rows that previously had reposted_by_name: null now get a
populated string when HarvestAPI returns the author info on any
known path. If HarvestAPI returns nothing on any path, the column
stays null and the diagnostic log fires once per run.
[1.4.4] - 2026-10-05
Changed - input form slimmed, three filters hidden from UI
Three input fields removed from the Apify input form but still read by
the Actor's code. The code path for each is unchanged - saved Tasks
with values set and API callers passing these keys continue to work
exactly as before. Only the form display changes.
posted_after_date - removed from form. Code at main.ts:307
still filters when the key arrives in input JSON.
posted_before_date - removed from form. Code at main.ts:308
still filters when the key arrives in input JSON.
content_contains - removed from form. Code at main.ts:309-312
still filters when the key arrives in input JSON.
Changed - date_filter enum trimmed
Removed "2years" and "3years" from date_filter enum. HarvestAPI's
/linkedin/company-posts endpoint only supports "1h", "24h",
"week", "month", "3months", "6months", "year" as
scrapePostedLimit values; the two longer windows were silently
ignored upstream and never filtered anything today. Removing them
from the dropdown prevents users from picking a value that produces
unfiltered results.
Why
The three hidden fields filter client-side AFTER HarvestAPI has returned
and billed the data. On narrow windows or sparse keyword matches, the
50-page pagination ceiling can be reached without the field delivering
enough rows to cover the HarvestAPI cost ($0.115 at the ceiling vs
~$0.104 revenue at 1% hit rate = loss). Hiding them from the form
removes the footgun from the default buyer flow while preserving
compatibility for anyone deliberately using them via JSON or API.
Backwards compatibility
Zero code change.src/main.ts still reads input.posted_after_date,
input.posted_before_date, input.content_contains via dynamic
property access. Apify preserves unknown JSON keys when storing and
passing input, so saved Tasks and API callers continue to work.
Zero pricing event change. The 7 billing events fire identically.
date_filter old values are safe. Any saved Task with
date_filter: "2years" or date_filter: "3years" keeps the stored
value and keeps running. The value passes through to HarvestAPI,
which silently ignores it (same behavior as before this release).
[1.4.3] - 2026-09-24
Changed - streaming output
Posts now stream to the dataset as each HarvestAPI page arrives,
instead of buffering the whole per-URL pool until every page is
fetched. Users see rows appear in the dataset within seconds of
starting the run, and aborted runs preserve every row already
pushed instead of losing everything.
Applies automatically when the run does not need the full pool:
sort_by is newest (default) or empty, and none of
include_post_extras, include_company_report, or
include_strategy_summary are on.
Batch mode preserved when the pool is required: sort_by=top
(ranks across the fetched pool), sort_by=oldest (reverses the
pool), or any of the aggregating enrichments. Behavior in batch
mode is unchanged.
Trade-off in streaming mode
The total_posts_for_company column is null on every streamed
row (the total is unknown until the last page arrives, and Apify
datasets are append-only so pushed rows cannot be updated).
Consumers who need the total can count rows per company_url
after the run. Every other field is populated identically to
batch mode.
Backwards compatibility
Every field key, default, output shape (except the null
total_posts_for_company note above), and pricing event is
unchanged.
Every existing saved Task, schedule, and API caller keeps
running. Runs that hit batch mode (sort_by=top or any
aggregating enrichment) behave exactly as before.
All 7 pay-per-event slugs fire identically. url-processed
charges once per URL, post-scraped charges per delivered post,
enrichment events charge per unit as before.
[1.4.2] - 2026-09-24
Changed - free-tier gating (breaking for free-tier users only)
Per-run post cap on the free Apify plan reduced from 50 posts to
5 posts. Applies only to free-tier accounts
(APIFY_USER_IS_PAYING != "1"). Paid tier is unaffected.
All opt-in enrichments are now disabled on the free Apify plan.
When a free-tier run turns on include_author_profile,
include_post_extras (or the deprecated
include_post_analytics / include_media_details aliases),
include_comments, include_company_report, or
include_strategy_summary, the toggles are silently overridden to
false and a status line names which were skipped. Paid tier is
unaffected.
Why
Apify's Actor.charge does not collect revenue from free-tier
accounts, but the Actor still pays HarvestAPI (posts, author
profiles, comments) and users still pay Anthropic (AI summary) on
every run. On the previous 50-post cap with enrichments allowed,
a single free-tier run with author profile enrichment could cost
the publisher ~$0.11 in HarvestAPI usage with $0.00 in revenue. The
new gate makes the free tier a strict preview: up to 5 posts, no
enrichments, ~$0.002 cost per URL.
Backwards compatibility
Every field key, default, output column, and pricing event is
unchanged.
Every existing saved Task, schedule, and API caller keeps running.
Paid-tier callers behave identically. Free-tier callers see fewer
rows (5 instead of 50) and their enrichment toggles are ignored
with a status message.
No pricing events changed. Free-tier runs simply do not fire the
enrichment events (they were $0 to the publisher anyway).
[1.4] - 2026-09-09
Added
Post analytics enrichment (include_post_analytics: true) -
adds engagement_rate (likes+comments+shares / author_followers),
post_performance_percentile (0-100 rank within the fetched pool),
posted_day_of_week, and posted_hour_utc columns to every post
row. Billed per post via post-analytics-added.
Media details enrichment (include_media_details: true) -
adds media_details_json column with a JSON array of per-image
and per-video metadata (URL, dimensions, order, video duration,
article thumbnail). Billed per post that has media via
media-details-added.
Comment scraping (include_comments: true +
max_comments_per_post) - populates top_comments_json +
top_comments_count columns using HarvestAPI's
/linkedin/post-comments endpoint. Default cap 0 = fetch every
available comment on each post (no hard ceiling). Billed per
comment fetched via comment-scraped.
Company report (include_company_report: true) - populates
company_report_json column on the first row per company URL
with posting cadence, best posting day and hour, top hashtags/
mentions, and company metadata (headline, industry, location,
followers). Billed per unique company URL via
company-report-added.
AI strategy summary (include_strategy_summary: true +
anthropic_api_key) - populates strategy_summary column on the
first row per company URL with a 3-paragraph AI-generated content
strategy summary. Uses Claude Haiku 4.5 via the user's own
Anthropic API key (~$0.015/company in tokens paid directly to
Anthropic). Billed per company via strategy-summary-added.
Compatibility
No field key renamed or removed. All new inputs default to
false / 0 / empty; existing scheduled Tasks are unaffected.
New output columns default to null on rows where the toggle is
off, so existing consumers are unaffected.
All new billing events are opt-in and only fire when the
corresponding toggle is on. Runs with no toggles set incur only
the existing url-processed + post-scraped charges.
5 new billing events: post-analytics-added ($0.001/post),
media-details-added ($0.001/post), comment-scraped
($0.001/comment), company-report-added ($1.00/company),
strategy-summary-added ($2.00/company). Configure on Apify's
Pricing tab before use.
All notable changes to this Actor are documented here. Format follows
Keep-a-Changelog. Dates are UTC. No field key is ever renamed or removed
between versions - existing saved Tasks, API integrations, and schedules
keep working.
[1.3] - 2026-09-06
Added
hashtags output column. Array of hashtags extracted from each
post's content. Populated via HarvestAPI's contentAttributes
structured entities (type: "HASHTAG"), with a regex fallback for
any tags HarvestAPI did not tag structurally. Case-insensitive
dedupe. Empty array on posts with no hashtags. No competitor in
the category returns this as a first-class column.
mentions output column. Array of company/person names
@-mentioned in each post's content. Extracted from
contentAttributes entries flagged COMPANY_NAME or
PERSON_NAME. Case-insensitive dedupe. Empty array on posts with
no mentions. Directly answers competitor complaint
more-data--mentions.
content_contains input. Optional case-insensitive keyword
filter on post content. Enter one or more keywords; only posts
whose text contains at least one are kept. Empty array (default)
means no filter. Directly answers competitor complaint
company-posts-search. Note: media-only posts with no text are
dropped when any keyword is set.
sort_by input. Optional select field with values newest
(default, matches previous behavior), oldest, and top. When
top is chosen the Actor fetches up to 3x the requested pool
before ranking by likes + comments + shares descending, so the
returned "top N" is meaningful rather than "top N of the newest
N". Default empty string preserves the previous newest-first
ordering exactly - no existing scheduled Task or API integration
changes behavior.
"What's new" callout above the fold in the README - top 4
v1.3 features (author profile enrichment, bare-handle input,
absolute date ranges, per-URL failure summary) surfaced right after
the version pill.
Workflow recipes section - 5 copy-paste JSON blocks for common
jobs (weekly competitor monitor, 100-company bulk export, deep
engagement analysis, range window, original-content-only
benchmarking). Every recipe runs on the current build with no
editing.
Integrations section - one-paragraph setups for Google Sheets,
Airtable, Zapier, Make, and n8n.
API and CLI usage examples - working snippets for curl, Python
(apify-client), and Node.js (apify-client). Cover start-and-wait
runs and dataset iteration.
Troubleshooting table - 10 common symptoms mapped to root cause
and one-liner fix (empty dataset, mixed-case slugs, 429 rate
limits, missing API key, unexpected billing, cap at 50 posts,
dedupe collapse, bare-handle edge cases).
Full output column reference table - all 32 output columns with
type, when-null behavior, and a concrete example value per column.
Turns the row-shape claim into a spec analysts can code against.
Maintenance signals rolled into the README: version pill, "Last
verified working" date, 24-hour business-day support SLA, 0 open
issues, and a Changelog section linking to this file with the last
two releases summarised inline.
SUPPORT.md documenting where to reach me, the
response SLA, what is in and out of scope, and the "no field key
renamed or removed" compatibility guarantee.
SECURITY.md documenting the responsible
disclosure policy, secret-handling behavior, and the
no-cookies / no-login guarantee.
.github/REPO_METADATA.md with the About-blurb, website URL,
and topic tags to paste into the GitHub repo Settings for
discoverability.
"Last verified" annotations on the Technical Details, Output
Reference, Output Schemas, and Maintenance sections so buyers can
see when each core claim was last re-checked.
author_public_id output column - LinkedIn public identifier
extracted from the author URL. Cheap join key for pairing post rows
with author profile data from other tools.
include_author_profile input toggle - when on, resolves each
unique author's HarvestAPI profile once (cached across the run), and
adds author_headline, author_industry, author_location, and
author_followers columns to every post row. Optional pay-per-event
hook: author-profile-fetched (no-op until configured on Apify).
Per-URL failure summary in end-of-run status message - up to 5
failed URLs listed by URL + HTTP status so the run's status bar
surfaces which URLs to inspect without opening the log.
Cost preview on run start - logs an up-front estimate: URLs at
$/URL, up to N posts at $/post, plus any extras enabled. Actual
billing is per real event delivered.
Removed
scrape_reactions, max_reactions, scrape_comments,
max_comments, comments_posted_limit input fields. These were
the "deep data (extra cost per post)" toggles. Removed because:
scrape_reactions was redundant with the always-populated
reactions column, which already contains the same per-type
breakdown as a compact string.
scrape_comments did not work on HarvestAPI's
/linkedin/company-posts endpoint: the response's comment array
came back empty regardless of the parameter, so the feature had
no effect for users.
reactions_breakdown and comments_details output columns
removed for the same reason. The reactions column keeps the
per-type counts as a string ("LIKE:142, PRAISE:38, ...").
reactions-fetched and comments-fetched billing hooks
removed. Only url-processed, post-scraped, and
author-profile-fetched remain.
Existing input JSON that still carries any of the removed keys is
silently ignored - no error - so saved Tasks that pin those values
continue to run without a schema change.
Fixed
Author profile enrichment now works for company authors too.
The previous build only enriched individual (/in/) authors, so runs
on company URLs (where the author is the company itself) returned
all-null enrichment columns. include_author_profile: true now
additionally calls HarvestAPI's /linkedin/company for each unique
company/school/showcase author and populates author_headline
(company tagline), author_industry, author_location (headquarters),
and author_followers.
is_repost detection now catches HarvestAPI reshares that have
a populated repostedBy object even when repostId is absent
(common on company-page reshares). Before, include_reposts: false
silently kept these rows because the detection missed them; now it
correctly filters them out.
Case-insensitive URL dedupe now normalizes www. and protocol
in addition to case and trailing slash. Previously
https://linkedin.com/company/Google and
https://www.linkedin.com/company/google were treated as different
URLs, which resulted in duplicate rows in the output.
reactions_breakdown column now populates from the reactions
array HarvestAPI returns at engagement.reactions when
scrape_reactions=true. Previously the extraction looked at
top-level raw.reactionsDetail/raw.reactions which HarvestAPI
does not populate, so the column stayed null even with the toggle
on.
comments_details column now checks additional HarvestAPI
response field candidates (commentsList, postComments, plus
variants inside engagement). Same root cause as reactions.
Changed
Store title now
LinkedIn Company Posts Scraper - Bulk Export [NOLOGIN] ✅
(57 chars). Swapped in - Bulk Export in place of
the [NO COOKIES & prefix to capture the high-intent "bulk
export" search term no competitor in the category claims. Kept the
[NO LOGIN] differentiator (higher search value than
[NOCOOKIES]
) and the ✅ marker. no cookies still appears in the
store description and the README H1 so buyers searching for that
term still hit the actor.
Store description rewritten around the new title: names the
three v1.3 columns (hashtags, mentions, author profile
enrichment) that no competitor in the subcategory returns,
advertises the >99% success rate up-front, and keeps
no login, no cookies
explicit.
Store description rewritten for SEO and to reflect current
features: names bulk scraping, engagement metrics, author profile
enrichment, bare-handle input, and the no-login / no-cookies
differentiators inside a single sentence.
Keyword tags expanded from 6 to 14 to cover primary keyword
variations (linkedin company posts scraper,
linkedin posts scraper, linkedin scraper), differentiators
(linkedin no login, linkedin no cookies), and intent categories
(competitor monitoring, content benchmarking, abm, b2b data).
Retry policy hardcoded at 3 attempts with 1s/2s/4s exponential
backoff (worst-case 7s wait per URL). This is a deliberate choice to
keep the user-facing surface simple and to cap HarvestAPI billing
exposure - a per-run tunable would let mis-configured runs burn
many extra calls with no upside.
Case-insensitive URL dedupe in normalizeUrls. Users pasting the
same LinkedIn URL in different casings (or with a trailing slash) no
longer end up with duplicate rows.
Retry list now covers 500 in addition to 429/502/503/504. Retry
delays follow exponential backoff based on max_retries.
Retry log lines include per-URL context ("attempt 1/3 [3/12]") so
bulk runs show which URL each retry is for.
Compatibility
No field key renamed or removed.
All existing saved Tasks continue to run identically. max_retries
and include_author_profile are optional; existing input JSON that
omits them behaves as before (3 retries, profile enrichment off).
New output columns (author_public_id, author_headline,
author_industry, author_location, author_followers) default to
null for existing consumers - no downstream schema needs to change.
[1.2] - 2026-09-06
Added
7 new input fields, all optional (no existing Task input needs to change):
Output row gained 3 columns: is_quote_post (boolean),
reactions_breakdown (JSON string, populated when
scrape_reactions=true), comments_details (JSON string, populated
when scrape_comments=true). Empty rows keep the same shape.
date_filter gained Last 2 years and Last 3 years window options.
companyUrls now accepts bare LinkedIn handles (e.g. google,
openai) and partial URLs (e.g. linkedin.com/company/google) in
addition to full URLs. Bare values auto-expand to
https://www.linkedin.com/company/<handle>.
Actor title now carries [NO COOKIES] [NO LOGIN] explicitly to
match store-listing convention.
Optional pay-per-event hooks: reactions-fetched and
comments-fetched. No-op until configured on the Apify pricing tab.
Changed
Numeric limit fields now follow the 0 = fetch everything convention:
max_posts default 0 (unchanged), schema maximum removed
max_reactions default 100 -> 0, schema maximum removed
max_comments default 50 -> 0, schema maximum removed
No hard ceiling in code either. Whatever positive number the user
enters is what runs.
Absolute date range wins over date_filter: if the user sets
posted_after_date or posted_before_date, date_filter is ignored
for that run and a warning is logged.
Input schema fields grouped by sectionCaption:
top: companyUrls, max_posts, date_filter
Date range (absolute cutoffs): posted_after_date,
posted_before_date
Include and exclude: include_quote_posts, include_reposts,
skip_empty_rows
Deep data (extra cost per post): scrape_reactions,
max_reactions, scrape_comments, max_comments,
comments_posted_limit
Titles and descriptions rewritten in plain English with a concrete
example in each field.
Compatibility
No input field key was renamed or removed.
Every new input is optional; input JSON that only carries
companyUrls runs identically to earlier versions.
Existing saved Tasks that pin max_reactions or max_comments to
a specific number continue to work; that number is still respected.
[1.1] - 2026-09-05
Added
Per-URL pay-per-event billing (url-processed) alongside per-post
(post-scraped), so URLs that return zero posts are not billed.
skip_empty_rows input.
Changed
Free-plan cap is now counted in posts (not dataset rows), still 50
posts per run.
API-key scrubbing centralised in src/secret.ts so keys never leak
to logs or dataset rows.
[1.0] - 2026-09-02
Initial release
LinkedIn Company Posts Scraper via HarvestAPI
(/linkedin/company-posts).
Inputs: companyUrls, max_posts, date_filter.
One flat row per post, 26 top-level columns.
Pay-per-event billing scaffold.
Structured error rows (type / message / fix) instead of thrown
errors, so a broken run still delivers a readable dataset.
![LinkedIn Company Posts Scraper - Bulk Export [NO LOGIN] ✅ avatar](https://images.apifyusercontent.com/cYtCOQf6cIFdPzMnw8y3S_FYLGH--Dk875pW7LUW4hk/rs:fill:250:250/cb:1/aHR0cHM6Ly9hcGlmeS1pbWFnZS11cGxvYWRzLXByb2QuczMudXMtZWFzdC0xLmFtYXpvbmF3cy5jb20vc0NDU2R3bm1LTUoxUTJzVG4tYWN0b3ItdVI0QmpoODNqcFNjZTRKNWQtMW9wMU1ucmI2TS1TcGFyc2VfaW5zdHJ1bWVudGF0aW9uX19kaXJlY3RfbHlyaWNzX191cmJhbl9yZWFsaXNtX195b3V0aGZ1bF9y.webp){kind=avatar}
![LinkedIn Ad Library Scraper [NO COOKIES] ✅ avatar](https://images.apifyusercontent.com/b-EEamuzq4m6vYFPC08m3s4pnfCs9LlPatL_X6rQ5qk/rs:fill:76:76/cb:1/aHR0cHM6Ly9hcGlmeS1pbWFnZS11cGxvYWRzLXByb2QuczMudXMtZWFzdC0xLmFtYXpvbmF3cy5jb20vc0NDU2R3bm1LTUoxUTJzVG4tYWN0b3ItcjlsRXNrczF4MVpJTG9RZWgtZXJGOHdUTEdHZy1TcGFyc2VfaW5zdHJ1bWVudGF0aW9uX19kaXJlY3RfbHlyaWNzX191cmJhbl9yZWFsaXNtX195b3V0aGZ1bF9y.webp){kind=avatar}
![LinkedIn Profile Posts Scraper - Bulk [NO COOKIES] ✅ avatar](https://images.apifyusercontent.com/OavDED5gNBRYMSWd9uEONykjVXz6b1U3Ew75sjoMKlU/rs:fill:76:76/cb:1/aHR0cHM6Ly9hcGlmeS1pbWFnZS11cGxvYWRzLXByb2QuczMudXMtZWFzdC0xLmFtYXpvbmF3cy5jb20vc0NDU2R3bm1LTUoxUTJzVG4tYWN0b3ItZ0huQXJqSlF1anIwWmZwdTkteHE3N1F0WEx1SC1jek5tY3kxd2NtbDJZWFJsTDNKaGQzQnBlR1ZzWDJsdFlXZGxjeTkzWldKemFYUmxYMk52Ym5SbGJuUXZiSEl2.webp){kind=avatar}
![LinkedIn Groups Scraper - Members, Admins & Posts [No Login] ✅ avatar](https://images.apifyusercontent.com/0uds2m_3UaumFHECvjdW-uhoEHqvmSAlHz_vv5annBg/rs:fill:76:76/cb:1/aHR0cHM6Ly9hcGlmeS1pbWFnZS11cGxvYWRzLXByb2QuczMudXMtZWFzdC0xLmFtYXpvbmF3cy5jb20vc0NDU2R3bm1LTUoxUTJzVG4tYWN0b3ItdEE5S09xaFg0N0hLdU9DdFktYXRwaG54eVFESC1wbmctY2xpcGFydC1jb21wdXRlci1pY29ucy1saW5rZWRpbi1sb2dvLWF0cmlvLXN5c3RlbXMtaW5jLWxpbmtl.webp){kind=avatar}
![LinkedIn Post Comment & Reaction Extractor [NO COOKIES] ✅ avatar](https://images.apifyusercontent.com/Ui3wLB4OtGL6cNa3H11VQAStZ9Fewq6t-oBZpMw0IjU/rs:fill:76:76/cb:1/aHR0cHM6Ly9hcGlmeS1pbWFnZS11cGxvYWRzLXByb2QuczMudXMtZWFzdC0xLmFtYXpvbmF3cy5jb20vc0NDU2R3bm1LTUoxUTJzVG4tYWN0b3ItY2tTeGZhTWZQNkZiZzc2ZGYtMnRWSk1vOTdaRS1oZC1zcXVhcmUtYmxhY2stb3V0bGluZS1saW5rZWRpbi1pY29uLXBuZy03MDE3NTE2OTUwNDU1NTM1Y3ppaXkx.webp){kind=avatar}