Start building

LinkedIn Profile Posts (full) API docs

Open Playground →

Start building

Send your first request

Platform API endpoint with unified authentication and usage tracking.

Production API
Platform API endpoint
https://api.sandbase.ai/v1/api/linkedin/profile-posts-full
Authorization header
Authorization: Bearer $SANDBASE_API_KEY
# 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-full" \
  -H "Authorization: Bearer $SANDBASE_API_KEY" \
  -H "Content-Type: application/json" \
  --data-binary @- <<'SANDBASE_JSON'
{
  "url": "https://www.linkedin.com/in/williamhgates/",
  "limit": 10,
  "includeReposts": true,
  "includeQuotePosts": true
}
SANDBASE_JSON
)
printf '%s\n' "$result"

2. Authentication

Set your SandBase API key in your server environment. Requests use Bearer authentication.

API key environment variable
export SANDBASE_API_KEY="YOUR_API_KEY"

Keep your key on the server. Do not expose it in browser code.

3. Parameters

urlstringrequired

Full URL of the public LinkedIn profile whose posts should be returned.

limitinteger

Most posts to return (1-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

cursorstring

Pagination cursor from a previous response's nextCursor.

postedLimitstring

Only return posts published within this relative time window.

Possible values: any, 1h, 24h, week, month, 3months, 6months, year

requireFieldsarray

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 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.

contextCountrystring

Regional LinkedIn context used when retrieving posts.

Possible values: any, US, GB, DE, FR

includeRepostsboolean

Whether to include reposts that share content without added commentary.

Default: true

postedLimitDatestring

Only return posts published on or after this date or timestamp, using a JavaScript-compatible date-time string.

includeQuotePostsboolean

Whether to include quote posts that add commentary to shared content.

Default: true

4. Response

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.