Skip to main content
POST
/
intents
/
leads
/
posts
Extract posts from a LinkedIn profile or company page
curl --request POST \
  --url https://app.prontohq.com/api/v2/intents/leads/posts \
  --header 'Content-Type: application/json' \
  --header 'X-API-KEY: <api-key>' \
  --data '
{
  "linkedin_url": "https://www.linkedin.com/in/john-doe",
  "limit": 5
}
'
{
  "posts": [
    {
      "author": "Jane Smith",
      "author_url": "https://www.linkedin.com/in/jane-smith",
      "content": "Post content text...",
      "id": "1234567890123456789",
      "urn": "urn:li:activity:1234567890123456789",
      "base_url": "https://www.linkedin.com/feed/update/urn:li:activity:1234567890123456789",
      "post_url": "https://www.linkedin.com/posts/jane-smith_post-title-activity-1234567890123456789-abcd",
      "published_at": "2026-03-11",
      "engagement_count": 142,
      "reactions_count": 128,
      "comments_count": 14
    }
  ]
}

​
Use Cases

  • Monitor content published by key prospects, customers, or their companies
  • Track thought leadership from individuals and brand pages
  • Analyze posting patterns and content strategy
  • Extract posts for further analysis or engagement tracking

​
Parameters

​
Required

  • linkedin_url: LinkedIn profile URL (e.g. https://www.linkedin.com/in/...) or company page URL (e.g. https://www.linkedin.com/company/...)
  • limit: Maximum number of posts to return (minimum: 1)

​
Optional

  • posted_within: last_24_hours, last_7_days, or last_30_days. Omit to return posts without this recency filter. Any other value returns 400.
The Pronto account used for the request must have valid LinkedIn credentials connected.

​
Response

The response is a JSON object with a posts array. Each post may include:
  • author: Post author name
  • author_url: LinkedIn URL of the author (profile or company)
  • content: Post text content
  • id: Post ID
  • urn: LinkedIn URN for the post
  • base_url: Base post URL
  • post_url: Full post URL
  • published_at: Date when the post was published (YYYY-MM-DD format)
  • engagement_count: Total engagement on the post (reactions + comments)
  • reactions_count: Number of reactions on the post
  • comments_count: Number of comments on the post
If the company ID or profile cannot be resolved from the URL, the API returns 200 with an empty posts array.

​
Example Request

curl --request POST \
  --url https://app.prontohq.com/api/v2/intents/leads/posts \
  --header 'Content-Type: application/json' \
  --header 'X-API-KEY: your-api-key' \
  --data '{
    "linkedin_url": "https://www.linkedin.com/in/profile",
    "limit": 5,
    "posted_within": "last_7_days"
  }'
For a company page, use the same field with the company URL, for example "linkedin_url": "https://www.linkedin.com/company/example".

​
Example Response

{
  "posts": [
    {
      "author": "Author Name",
      "author_url": "https://www.linkedin.com/in/author-profile",
      "content": "Post content text...",
      "id": "1234567890",
      "urn": "urn:li:activity:1234567890",
      "base_url": "https://www.linkedin.com/feed/update/...",
      "post_url": "https://www.linkedin.com/posts/...",
      "published_at": "2026-01-15",
      "engagement_count": 142,
      "reactions_count": 128,
      "comments_count": 14
    }
  ]
}

​
Errors (400)

  • Missing limit: Missing required keys: limit
  • Missing linkedin_url: Missing required keys: linkedin_url
  • Invalid posted_within: Invalid posted_within. Use last_24_hours, last_7_days, last_30_days, or omit the key.

​
Notes

  • Synchronous response (200 OK) with { "posts": [...] }
  • Recency filtering is applied after posts are fetched from LinkedIn

Authorizations

​
X-API-KEY
string
header
required

Body

application/json
​
linkedin_url
string<uri>
required

LinkedIn profile URL (e.g. /in/...) or company page URL (e.g. /company/...)

Example:

"https://www.linkedin.com/in/john-doe"

​
limit
integer
required

Maximum number of posts to return

Required range: x >= 1
Example:

5

​
posted_within
enum<string>

Only include posts published within this window. Omit for no recency filter.

Available options:
last_24_hours,
last_7_days,
last_30_days

Response

Successfully extracted posts

​
posts
object[]

Posts from the profile or company page, after optional recency filtering