How is company competitor engagement different from person competitor engagement?
The company endpoint starts from a company or page context. The person endpoint evaluates engagement from a person-centered workflow.
Find people who have demonstrated engagement around a company page and return their available profile URLs with post context. Supply a company_url plus optional result and sorting controls. The request is queued asynchronously and returns a request_id; poll the status endpoint or supply a callback_url. Results are person-first engagement items with linkedin_profile_url, person details, post date/context, and aggregate engagement metrics; people identified as current employees of the requested company are excluded when current-organization data is available. Callback delivery is best effort - keep the returned request_id and use the status endpoint for the final result. Credits are charged per person engagement result returned.
Manual credentials take precedence over your account key.
The Company Competitor Engagements API finds people engaging with a company or competitor page, turning public social activity into account and prospecting signals.
recent (default) or top.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 as a query parameter:
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 |
|---|---|---|
| Competitor Engagements | 5 | Charged per person engagement result returned (per-result) |
| No results | 0 | No person profile results never burns per-result credits |
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": "65f6d9f92799d3c2a24123f4f13a7d7a_1700000123_8810",
"status": "completed",
"completed": true,
"result": {
"results": [
{
"linkedin_profile_url": "https://www.linkedin.com/in/janedoe",
"person": {
"name": "Jane Doe",
"organizations": [
{
"name": "Example Software",
"title": "Head of Growth"
}
]
},
"interaction_type": "company_post",
"post_date": "2026-01-10T15:30:00Z",
"engagement_metrics": {
"likes": 24,
"comments": 3,
"shares": 1
}
}
],
"total_results": 1
},
"completed_on": "2026-01-15T10:35:00Z"
},
"timestamp": "2026-01-01T00:00:00"
}