linkedin/
search-posts

The LinkedIn Search Posts API discovers Google-indexed public LinkedIn posts by keyword and optional relative date, with normalized content, authors, media, tags, timestamps, and visible engagement.

LinkedIn Search Posts API

Keyword discovery
Relative date
Canonical posts
0.5 credits / result
Ready
Ready

Enter parameters and send a request. The task status and normalized results will appear here.

README

By SocQ · Updated

LinkedIn Search Posts

LinkedIn Search Posts uses an upstream Google-indexed discovery method to find public pages for one keyword query and then extracts available post records. The result is a ranked, collection-time sample rather than LinkedIn's personalized native search or a complete archive, so it should not be treated as total conversation volume, reach, sentiment, or share of voice.

LinkedIn Search Posts API Features

  • Keyword-led discoverySearch publicly indexed LinkedIn pages with one required non-empty topic, organization, product, person, or phrase query.
  • Optional relative dateForward a date_posted string to the provider; documented values include last-hour, last-day, last-week, last-month, and last-year.
  • Page-aligned limitsSet results_limit from 10 through 2000 in multiples of 10; the default is 10 and accepted values do not guarantee provider coverage.
  • Canonical post recordsEvery LinkedIn Search Posts API result carries stable content, author, metric, media, hashtag, mention, publication, and collection fields.
  • Cursor-aware collectionFollow provider cursors until the requested cap, a final or empty page, a missing cursor, or a repeated cursor stops collection.

LinkedIn Search Posts API Parameters

ParametersRequiredDescription
queryRequiredRequired non-empty keyword or phrase used for public indexed-post discovery.
date_postedOptionalOptional non-empty relative-date string forwarded to the provider. SocQ does not independently enforce the provider's documented values.
results_limitOptionalOptional integer result cap. It defaults to 10, accepts 10 through 2000, and must be a multiple of the provider's 10-record page size.

How to Use the LinkedIn Search Posts API

Submit one keyword query to the LinkedIn Search Posts API, poll the asynchronous task, and review the returned discovery sample.

  1. Choose one non-empty query and optionally select a provider relative-date string.
  2. POST query, date_posted, and a 10-record increment to /v1/linkedin/search-posts, then save task_id.
  3. Poll /v1/tasks/{task_id} until the task reaches a terminal status.
  4. On success, process data.results.items and follow next_cursor whenever has_more is true.
curl -X POST "https://api.socq.ai/v1/linkedin/search-posts" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"AI agents","date_posted":"last-week","results_limit":10}'

# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is true

LinkedIn Search Posts API Use Cases

  • Topic discovery: Use the LinkedIn Search Posts API to find publicly indexed posts that mention a selected topic, product, organization, person, or phrase.
  • Message and format review: Inspect returned claims, hashtags, authors, links, and media formats without treating the sample as comprehensive.
  • Author and URL triage: Identify public authors and post URLs for manual follow-up or author-specific collection.
  • Discussion handoff: Select relevant result URLs and pass them to LinkedIn Post Comments when public discussion records are needed.

LinkedIn Search Posts API Pro Tips

  • Use the same query, date string, result limit, and collection schedule when comparing LinkedIn Search Posts API samples.
  • Treat upstream order as search ranking, not a neutral popularity, recency, or relevance score.
  • Do not interpret a successful empty result as proof that no matching LinkedIn post exists.
  • Verify important text and media on the source post because indexed pages can be stale, truncated, deleted, or restricted.
  • Treat missing engagement values as unknown rather than zero, and retain collected_at with every snapshot.
  • Use company-posts or profile-posts when the target publisher is already known.

Beyond the LinkedIn Search Posts API, use these APIs when you need a different type of public LinkedIn data.

  • LinkedIn Profiles API — Normalize public profile identity, roles, location, visible audience counts, experience, education, and skills from profile URLs.
  • LinkedIn Companies API — Normalize public company descriptions, websites, logos, visible audience and employee counts, industries, locations, and specialties.
  • LinkedIn Posts API — Collect public post text, authors, visible engagement, media, publication time, type, and hashtags from supported URLs.
  • LinkedIn Jobs API — Normalize public job titles, companies, descriptions, locations, qualifications, employment details, application links, and available salary fields.
  • LinkedIn Post Comments API — Collect public comments exposed with a known LinkedIn post, including text, author context, timestamps, relationship IDs, and visible likes and reply counts.
  • LinkedIn Search People API — Discover candidate public profiles from LinkedIn people-search URLs, returning normalized identity, description, images, location, website, account signals, and available metrics.

Explore other platforms

Combine LinkedIn data with public data from other supported social platforms.

LinkedIn Search Posts API — FAQ

LinkedIn Search Posts API is a programmatic interface for discovering Google-indexed public LinkedIn posts from one keyword query and an optional relative-date string. It returns normalized post content, authors, media, tags, timestamps, and visible engagement.

Yes. query must be a non-empty string. The endpoint does not expose native author, company, language, content-type, engagement, or sort filters.

The provider documents last-hour, last-day, last-week, last-month, and last-year. SocQ forwards non-empty strings without independently enforcing that enum, so other values remain provider-dependent.

It must be an integer from 10 through 2000 and a multiple of 10. The default is 10.

No. Google indexing, public availability, provider cursor limits, empty pages, and repeated or missing cursors can stop collection earlier.

No. This endpoint emits normalized post records. Use LinkedIn Post Comments for the public discussion under a selected post URL.

Each returned post costs 0.5 SocQ credits, with no base charge. The default estimate is 10 results, empty result sets have no result charge, and actual usage may exceed the estimate when permitted.