https://api.nexscope.ai/social/linkedin/search/postsRun this API
Send a JSON request to execute this API and receive the documented response payload.
Endpoint
| Method | POST |
| Path | https://api.nexscope.ai/social/linkedin/search/posts |
| Auth | Bearer API key |
| Content-Type | application/json |
Request parameters
| Name | Type | Required | Description |
|---|---|---|---|
query | string | required | Keyword or phrase to search for in public LinkedIn posts Example: ai agents |
date_posted | string | optional | Date posted filter based on Google-indexed results |
cursor | string | optional | The cursor returned from the previous response. The maximum cursor is 11; cursor 12 or greater returns a 400 response. |
Social data contract
Use your Nexscope API key. No supplier credentials are required. Requests reject unknown fields, including pageSize. URLs require HTTPS and an exact supported platform host and resource path. Documented YouTube video URLs may use youtu.be; other short links are unsupported. Check the request schema for supported fields and defaults.
Each request fetches one page. Continue manually with the returned nextCursor, or nextPage for Instagram Reels (pages 1–11). Cursors are opaque, unchanged strings up to 65536 UTF-8 bytes. No automatic pagination, retry, media download or transcription is performed. Repeated requests may purchase data again.
Resource status is independent of HTTP and billing: AVAILABLE, PARTIAL, PRIVATE, RESTRICTED, NOT_FOUND, NO_TRANSCRIPT or UNKNOWN can accompany code 0. Unknown values remain null; arrays remain empty arrays. fetchedAt is the response observation time; sourceFetchedAt is null without source evidence.
usage.billingStatus is NOT_CHARGED, SETTLED or UNKNOWN; chargedCredits is null when unconfirmed. Unknown charges never mean free. Completed lookups have a minimum charge of 10 credits, including cached, no-caption and unavailable-resource results; check API usage records for the actual charge. Parameter errors and unpublished APIs use the standard error envelope; upstream failures use code 13007, rate limits 429 and timeouts 408. Always check code and msg.
Response example
Platform response envelope. code 0 indicates success or acceptance; data contains the business result.
{
"code": 0,
"cost": "-1",
"data": {
"data": {
"cursor": "2",
"posts": [
{
"author": {
"followers": 313422,
"image": "https://media.licdn.com/dms/image/v2/D5603AQGl7mUqMgCLRQ/profile-displayphoto-scale_200_200/B56Z3V9cKNKgAc-/0/1777411150180?e=2147483647&v=beta&t=oVB3kzDdrFGH-2pOYeziFk3m_B8fTCiH190YbTMrgoY",
"name": "Aakash Gupta",
"url": "https://www.linkedin.com/in/aagupta"
},
"commentCount": 25,
"comments": [
{
"author": "Lewin Wanzer",
"datePublished": "2025-08-02T01:23:21.112Z",
"id": "7357219423591563264",
"linkedinUrl": "https://www.linkedin.com/in/lewinwanzer",
"publishedTimeAgo": "1y",
"reactionCount": 0,
"text": "Thanks for sharing, Aakash. Appreciate the breakdown—but here’s the twist most are missing: the AI agent is Agent Smith.\nThe more we chase “smart tasks” without structure, the more we lose the plot. Developers are confused. “AI Architects” don’t exist. And agents are now doing things they were never cleared to do.\nWe don’t need more tools—we need orchestration, identity-bound execution, and governed outcomes. Tourque will set the standard. Until that’s the norm, it’s just hype on autopilot.",
"urn": "urn:li:comment:(urn:li:ugcPost:7354600336214376448,7357219423591563264)"
}
],
"datePublished": "2025-07-25T19:56:02.566Z",
"description": "There's way too much hype about AI agents.\n\nHere's your simple guide:\n\nForget the super complex taxonomies out there. There are 4 categories of tools you should know.\n\n1. Consumer Agents\n\nThe latest LLMs, like Grok and Claude, have agents built-in. ChatGPT is rolling out the 'Agent' tool to paid plans as we speak.\n\nThese are best for:\n\n- Ad-hoc analysis\n- Quick research tasks\n- Content creation (PRDs, strategy docs)\n\n2. No-Code Agent Builders\n\nThere is a new class of tools that you must know. Tools like Zapier and Lindy offer where you can do things like connecting your Gmail to Claude.\n\nBe sure to explore these for:\n\n- Email triage\n- Competitor monitoring\n- Automated data reporting\n\n3. Developer-First Platforms\n\nAll the tools you've heard like CrewAI, Langchain, and Autogen are great frameworks for developers. Think of them as the React/Node for agents.\n\nThey're for:\n\n- Customer-facing agents\n- Deep system integrations\n- Complex, proprietary business logic\n\n4. Specialized Agent Apps\n\nTools like Cursor, Otter, and Jasper are specialized agent apps. They're supported by complex business logic to do one task really well.\n\nMy recommendations:\n\n- Coding → Cursor\n- Meetings → Otter AI\n- Research → Perplexity\n\nReady to go the layer deeper? I teamed up with AI PM at Meta Vikash Rungta to write you the web's most practical and simple guide: https://lnkd.in/eeey5Cxr\n\nPlease, let's end all the hype and talk real use cases.\n\nP.S. What agent are you using most?",
"image": "https://media.licdn.com/dms/image/v2/D4E1FAQHAzpgC7eaKgw/feedshare-document-images_160/B4EZhDHPPEGoAs-/1/1753472629037?e=1780531200&v=beta&t=7UAmCkScn1TSkvHB9HxLTPoBV7wibupD2WlKSec3ork",
"images": [
"https://media.licdn.com/dms/image/v2/D4E1FAQHAzpgC7eaKgw/feedshare-document-images_160/B4EZhDHPPEGoAs-/1/1753472629037?e=1780531200&v=beta&t=7UAmCkScn1TSkvHB9HxLTPoBV7wibupD2WlKSec3ork"
],
"likeCount": 217,
"media": "https://media.licdn.com/dms/image/v2/D4E1FAQHAzpgC7eaKgw/feedshare-document-images_160/B4EZhDHPPEGoAs-/1/1753472629037?e=1780531200&v=beta&t=7UAmCkScn1TSkvHB9HxLTPoBV7wibupD2WlKSec3ork",
"url": "https://www.linkedin.com/posts/aagupta_what-you-need-to-know-ai-agents-activity-7354600338621906944-RvXR"
}
],
"query": "ai agents",
"success": true
},
"platform": "linkedin",
"resourceStatus": "AVAILABLE",
"usage": {
"billingStatus": "UNKNOWN"
}
},
"msg": null,
"time": "2026-01-01 00:00:00",
"traceId": null,
"ts": "0"
}Response fields
| Name | Type | Required | Description |
|---|---|---|---|
code | integer | required | 0 means accepted or successful; nonzero is a platform error. |
cost | string | required | Elapsed milliseconds, never credits; -1 outside web requests. |
data | any | required | Data value used by this API operation. |
msg | string | null | required | Msg value used by this API operation. |
time | string | required | Server local time: yyyy-MM-dd HH:mm:ss. |
traceId | string | null | required | Trace id value used by this API operation. |
ts | string | required | Epoch milliseconds. |
Any of option 1 — requires platform, resourceStatus, data, usage
| Name | Type | Required | Description |
|---|---|---|---|
data | object | required | Data value used by this API operation. |
data.data | object | required | Data value used by this API operation. |
data.platform | string | required | Platform value used by this API operation. |
data.resourceStatus | string | required | Resource status value used by this API operation. |
data.usage | object | required | Usage value used by this API operation. |
Any of option 2
| Name | Type | Required | Description |
|---|---|---|---|
data | null | required | Data value used by this API operation. |
Responses
| Code | Description |
|---|---|
| 200 | Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result. |
| 429 | Execution admission rate limit; honor Retry-After when present. |
| 503 | Execution admission is temporarily unavailable; honor Retry-After when present. |
| Opt-in | X-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing API key (code 11209), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses. |
Data source, freshness, and limitations
Source, freshness, coverage, rate limits, and estimation notes are not specified in this API definition unless they appear in the request or response field documentation above. Do not assume official marketplace data or real-time freshness when it is not explicitly documented.