What does a social media posts API return?
It returns recent public posts and related metadata from resolved social profiles, subject to available sources.
API Log in Get API keyReturns recent social posts and engagement data for a profile URL on a supported social media site. The request is queued and returns a request_id (status processing, or pending when a callback_url is supplied); poll the status endpoint or wait for the callback.
Manual credentials take precedence over your account key.
The Social Newsfeed API pulls recent public posts from a person's resolved social profiles for monitoring, personalization, and context-aware outreach.
YYYY-MM-DD. Posts without a parseable date are always included.This endpoint is asynchronous. A successful submit returns a request_id while the job runs in the background. Poll the same path with a GET request - same authentication headers - passing the request_id and any
endpoint-specific page values shown below as query parameters:
Each poll returns the job's current status; once it is completed the payload carries the result shown under Responses. Polling an
unknown or expired request_id returns 404 request_not_found.
| Status | Meaning |
|---|---|
| queued · processing · pending | The job is still running - keep polling. |
| completed | The job finished; the payload carries the result and completed: true. |
| failed | Terminal - the job could not complete; the error field explains why. |
Poll every few seconds at first, backing off for long-running jobs. Polling is free - status checks never burn credits.
callback_url parameter and the completed payload is POSTed to your endpoint
when the job finishes - no polling required. Delivery is retried up to 5 times with exponential backoff (1s,
5s, 15s, 1m, 5m) and a 30-second timeout per attempt; respond with a 2xx status to acknowledge receipt.Credits are charged based on the matched configuration. The listed cost is the per-result unit price.
| Feature | Credits | Notes |
|---|---|---|
| Newsfeed | 2 | 2 credits per 10 posts returned, rounded up (e.g. 1-10 → 2, 11-20 → 4, up to ~200) |
| No posts | 0 | Credits scale with posts actually returned, not requested |
A successful response wraps the payload in the { success, data, timestamp } envelope (also shown live in the panel on the right):
{
"success": true,
"data": {
"request_id": "newsfeed_a1b2c3d4e5f6a1b2_1717000000_4271",
"status": "completed",
"completed": true,
"result": {
"url": "https://linkedin.com/in/janedoe",
"newsfeed": [
{
"id": "post_123456",
"source": "linkedin",
"content": "Excited to announce our new AI-powered analytics platform!",
"timestamp": "2026-01-14T15:30:00Z",
"url": "https://linkedin.com/feed/update/urn:li:activity:123456",
"likes": 142,
"comments": 18,
"shares": 9
}
]
},
"completed_on": "2026-01-15T10:35:00Z"
},
"timestamp": "2026-01-01T00:00:00"
}