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.

9 events covered

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

Signature header
X-LI-Signature

Format: <lowercase hex>

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

Docs ↗
Signed material
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.

How events are identified
type field in the body; leadAction or action says what happened
Body format
JSON

Content type: application/json.

Event families
Lead Sync notifications, Organization social action notifications, Talent Apply Connect applications, Talent Job Posting callbacks, Talent Middleware push events
URL handshake
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.

Envelope
type
Agent skill
npx skills add hookdeck/webhook-skills --skill linkedin-webhooks

Verify LinkedIn webhooks →

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/eventSubscriptions for 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 a jobApplicationWebhookUrl in 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

  1. 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 challengeCode and an HMAC of it as challengeResponse within 3 seconds, as JSON with a 200.

    Testing your endpoint →
  2. 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 →
  3. Lead Sync deliveries have no notificationId

    LinkedIn's general advice is to deduplicate on the notification ID, but LEAD_ACTION doesn't have one. Use leadGenFormResponse and occurredAt together, because one member's register and unregister actions share a response URN.

    Handle duplicates →
  4. 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

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

EXPORT_CANDIDATE_PROFILE · EXPORT_APPLICATION_EVALUATION · EXPORT_JOB_APPLICATION · JOB_POSTING_STATUS +3

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.

Not affiliated with LinkedIn. Facts are compiled from public sources and linked inline.