LinkedIn webhooks
LinkedIn webhooks are signed JSON POSTs that LinkedIn sends about lead form responses, activity on Company Pages, and job and candidate events in its Talent products.
How LinkedIn webhooks work
Webhooks save you polling LinkedIn's APIs for changes, but they're only open to apps with an approved use case, and each product has its own access and its own way to register a URL. Lead Sync, Community Management, Apply Connect, Job Posting, Recruiter System Connect and CRM Connect are separate, so most apps only ever see a few of these events. LinkedIn sends a GET challenge before it delivers anything, then repeats it about every 2 hours, and blocks the endpoint after 3 failures in a row.
Each delivery is a JSON POST, and type in the body names the event. LEAD_ACTION has a leadAction of CREATED or DELETED. ORGANIZATION_SOCIAL_ACTION_NOTIFICATIONS holds a notifications array in batches of up to 10, each with its own action. Many Talent events carry only an id that you use to fetch the details with a second API call. There is no version header or field on a delivery.
Key facts
HMAC-SHA256 Docs discrepancy
The Apply Connect page says to add the hmacsha256= prefix to your computed signature for a complete match. The shared Webhooks page says the header holds only the hex digest, and the sample headers on the Talent pages are bare hex. Follow the shared page, and hash the bytes as received.
hmacsha256={raw body} The literal string hmacsha256=, then the POST body exactly as received, with no timestamp added. The prefix never appears in the header.
type field in the body; leadAction or action says what happened Lead Sync notifications, Organization social action notifications, Talent Apply Connect applications, Talent Job Posting callbacks, Talent Middleware push events GET: sign the challenge HTTP 200 within 3 seconds, with Content-Type: application/json and a JSON body holding challengeCode and challengeResponse, the lowercase hex HMAC-SHA256 of the challengeCode keyed with your clientSecret. After 3 failed re-validations in a row, the endpoint is blocked.
Setting up LinkedIn webhooks
- For Community Management and Job Posting, register your URL in the Webhooks tab of your app in the Developer Portal, which only appears with an approved webhook use case. Community Management then needs a
PUT /rest/eventSubscriptionsfor each member. - Lead Sync can't be set up in the portal: create the subscription with
POST /rest/leadNotifications, and LinkedIn recommends doing it per owner. Apply Connect takes ajobApplicationWebhookUrlin the job payload, and Recruiter System Connect takes callback URLs during customer configuration. - LinkedIn needs a public HTTPS URL and doesn't support ngrok. It recommends testing with serverless functions on a cloud provider, or you can forward to localhost from an Event Gateway source with the Hookdeck CLI. Campaign Manager can generate test leads.
- LinkedIn's docs describe no way to resend a delivery. You can re-run validation from the portal, and Community Management keeps notifications you can pull for 60 days.
Delivery behaviour
3s for the challenge no timeout is documented for a POST delivery Retries varies by product Community Management: every 5 minutes for 8 hours After retries varies by product Community Management keeps 60 days to pull; Talent push events are dropped Duplicates expected the key differs by product, and Lead Sync has no notification id Known failure modes
From Hookdeck's LinkedIn guide →-
No webhooks ever arrive
LinkedIn only sends to a URL that has passed its GET challenge, so a POST-only route never receives an event. Return
Testing your endpoint →challengeCodeand an HMAC of it aschallengeResponsewithin 3 seconds, as JSON with a200. -
The endpoint stops receiving events after working for weeks
LinkedIn re-validates about every 2 hours and blocks an endpoint after 3 failures in a row, so a few hours of downtime can stop delivery. Fix the cause, then re-run validation from the Developer Portal.
Retries and blocked endpoints → -
Lead Sync deliveries have no notificationId
LinkedIn's general advice is to deduplicate on the notification ID, but
Handle duplicates →LEAD_ACTIONdoesn't have one. UseleadGenFormResponseandoccurredAttogether, because one member's register and unregister actions share a response URN. -
Community Management notifications stop for one member
A subscription lasts only as long as the member's grant and admin role, and LinkedIn's docs describe no event when it's removed. Check subscriptions on a schedule, resubscribe, then query the notifications you missed.
Choosing events →
LinkedIn webhook best practices
- Verify every signature.
Compute the HMAC over
hmacsha256=plus the raw body with yourclientSecret, so a forged POST can't reach your handler. - Keep the challenge handler small. It has 3 seconds to respond, about every 2 hours, so it should do nothing except compute one HMAC.
- Return a 200 and process in the background. The shared docs accept any 2xx, but the Talent pages only treat a 200 as success, so a 200 is safe everywhere.
- Use the right duplicate key for each product.
notificationIdonly exists on Community Management. Lead Sync needsleadGenFormResponseandoccurredAttogether. - Act on the warning emails. LinkedIn emails the app's developers about each failed validation, and that's your chance to fix it before the endpoint is blocked.
- Track subscriptions for each member. A Community Management subscription ends when the member's grant lapses or they stop being an admin, and LinkedIn's docs describe no event for it.
Common LinkedIn webhook events
Lead Sync
LEAD_ACTION | Lead form response is created or deleted |
Community Management
ORGANIZATION_SOCIAL_ACTION_NOTIFICATIONS | Likes, comments, shares or mentions on a Company Page |
Talent
EXPORT_JOB_APPLICATION | Applicant submits an application to your posted job |
JOB_POSTING_STATUS | Job's listing, Easy Apply or promotion status changes |
EXPORT_CANDIDATE_PROFILE | Candidate is exported from Recruiter to your ATS or CRM |
Events by resource
| Resource | Events | Payloads |
|---|---|---|
talent | 7 | 7 |
1 more resource, including Other LinkedIn events. All 9 events →
In this hub
| Webhook events → | Every covered LinkedIn event, with payloads where the registry has them. |
| MCP events → | How an agent subscribes to LinkedIn events as MCP events. |
| Verify signatures → | Signature facts, verification code and common failures. |
| Production guide → | Production problems: timeouts, duplicates, ordering and retries, and how to handle them. |
| Agent skill → | Install the webhook skill in your coding agent. npx skills add hookdeck/webhook-skills --skill linkedin-webhooks |
Keep a failed re-validation from blocking your LinkedIn endpoint.
Hookdeck Event Gateway answers LinkedIn's GET challenge once the source has your client secret, verifies the signature, queues events and retries to your service on your schedule.