urlstringrequired
Full URL of the public LinkedIn profile whose posts should be returned.
https://api.sandbase.ai/v1/api/linkedin/profile-posts-thinFetch recent public LinkedIn profile posts with portable identity, author, engagement, article, image, video, and repost fields.
Your output will appear here
Complete the inputs, then click Run.
Fetch recent public LinkedIn profile posts with portable identity, author, engagement, article, image, video, and repost fields.
curl -X POST "https://api.sandbase.ai/v1/api/linkedin/profile-posts-thin" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url": "https://www.linkedin.com/in/williamhgates/", "limit": 10}'
The result is returned in outputs[0].data. A lookup that finds nothing still succeeds and returns found: false.
| Name | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Full URL of the public LinkedIn profile whose posts should be returned. |
cursor | string | No | Pagination cursor from a previous response's nextCursor. |
limit | integer | No | Most posts to return (10-100, default 10). Ignored on sources that page: each call returns one full page of 50 posts; follow nextCursor for more. Sources that cannot page return up to limit posts in one call with no ne |
requireFields | array | No | Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example nextCursor, and it is served only by a source that returns every one |
Billed at the actual cost of each call, usually $0.005 per request. A call can cost more when the first data source fails and another one answers. Failed calls are not charged. Lookups that find nothing and searches with no results are billed at their actual cost, which is often lower and can be $0.
Start building
Platform API endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/api/linkedin/profile-posts-thin" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"url": "https://www.linkedin.com/in/williamhgates/",
"limit": 10
}
SANDBASE_JSON
)
printf '%s\n' "$result"Set your SandBase API key in your server environment. Requests use Bearer authentication.
export SANDBASE_API_KEY="YOUR_API_KEY"Keep your key on the server. Do not expose it in browser code.
urlstringrequiredFull URL of the public LinkedIn profile whose posts should be returned.
limitintegerMost posts to return (10-100, default 10). Ignored on sources that page: each call returns one full page of 50 posts; follow nextCursor for more. Sources that cannot page return up to `limit` posts in one call with no nextCursor.
Default: 10
cursorstringPagination cursor from a previous response's nextCursor.
requireFieldsarrayOptional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `nextCursor`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a profile that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge. On a paginated walk it applies to the first page only; later pages stay with the source that page chose, at the price it was quoted.
Saved example response for this API; no live request is made when viewing it.
No saved response has been published. Run the API in Playground to inspect its response.
Explore more
| API | Price | Response |
|---|---|---|
LinkedIn Profile Posts (basic)This API LinkedIn | From $0.005 per call | JSON |
LinkedIn | From $0.0012 per call | JSON |
LinkedIn | From $0.03 per call | JSON |
LinkedIn | From $0.0012 per call | JSON |
LinkedIn | From $0.0057 per call | JSON |
LinkedIn | From $0.0026 per call | JSON |
Questions
Send a POST request to https://api.sandbase.ai/v1/api/linkedin/profile-posts-thin with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.
From $0.005 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.
Required: url (string). Optional: limit (integer), cursor (string) and requireFields (array). The Parameters table and the Playground on this page list every field.
A JSON response returned in the same HTTP request (synchronous).
No. LinkedIn Profile Posts (basic) runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for LinkedIn API access separately.