LinkedIn webhook events
9 LinkedIn event types in 1 resource, plus Other LinkedIn events. 9 have sample payloads.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
talent
EXPORT_CANDIDATE_PROFILE
documented from LinkedIn docs (example)
EXPORT_CANDIDATE_PROFILE Candidate is exported from Recruiter to your ATS or CRM
Identified by type field in the body; leadAction or action says what happened
Resource talent
{
"id": "59a92119-3b72-4d2f-8e12-137a13180df6-1",
"type": "EXPORT_CANDIDATE_PROFILE",
"expiresAt": 1481402799192
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | 59a92119-3b72-4d2f-8e12-137a13180df6-1 |
type | string | EXPORT_CANDIDATE_PROFILE |
Full schema: 3 fields.
From LinkedIn docs
-
Content type
application/json
EXPORT_APPLICATION_EVALUATION
documented from LinkedIn docs (example)
EXPORT_APPLICATION_EVALUATION LinkedIn evaluates an application for your job posting
Identified by type field in the body; leadAction or action says what happened
Resource talent
{
"id": "59a92119-3b72-4d2f-8e12-137a13180df6-1",
"type": "EXPORT_APPLICATION_EVALUATION",
"expiresAt": 1765091130000
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | 59a92119-3b72-4d2f-8e12-137a13180df6-1 |
type | string | EXPORT_APPLICATION_EVALUATION |
Full schema: 3 fields.
From LinkedIn docs
-
Content type
application/json
EXPORT_JOB_APPLICATION
documented official schema
EXPORT_JOB_APPLICATION Applicant submits an application to your posted job
Identified by type field in the body; leadAction or action says what happened
Resource talent
{
"type": "EXPORT_JOB_APPLICATION",
"externalJobId": "jobIdOnAtsPartner",
"jobApplicationId": "urn:li:jobApplication:12345678",
"jobApplicant": "urn:li:person:abc123",
"appliedAt": 1602137400011,
"applicantSkills": [ … ],
"questionResponses": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | EXPORT_JOB_APPLICATION |
Full schema: 57 fields.
From LinkedIn docs
-
Content type
application/json
JOB_POSTING_STATUS
documented from LinkedIn docs (example)
JOB_POSTING_STATUS Job's listing, Easy Apply or promotion status changes
Identified by type field in the body; leadAction or action says what happened
Resource talent
{
"developerApplicationUrn": "urn:li:developerApplication:12345",
"externalJobPostingIds": "{external_job_posting_id_1}",
"type": "JOB_POSTING_STATUS",
"listedAt": 1602137400011,
"externalJobPostingId": "{external_job_posting_id_1}",
"location": "Sunnyvale, California",
"listingStatus": "LISTED",
"linkedInApplyStatus": "ENABLED",
"jobPostingUrl": "https://www.linkedin.com/jobs/view/123"
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | JOB_POSTING_STATUS |
Full schema: 17 fields.
From LinkedIn docs
-
Content type
application/json
RESYNC_JOBS
documented from LinkedIn docs (example)
RESYNC_JOBS LinkedIn asks you to re-sync one or more jobs
Identified by type field in the body; leadAction or action says what happened
Resource talent
{
"developerApplicationUrn": "urn:li:developerApplication:12345",
"externalJobPostingIds": [ … ],
"syncAllOpenJobs": false,
"type": "RESYNC_JOBS"
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | RESYNC_JOBS |
Full schema: 5 fields.
From LinkedIn docs
-
Content type
application/json
INTEGRATION_STATUS_CHANGE
documented from LinkedIn docs (example)
INTEGRATION_STATUS_CHANGE Customer enables a Recruiter System Connect integration
Identified by type field in the body; leadAction or action says what happened
Resource talent
{
"id": "{Unique Notification ID}",
"type": "INTEGRATION_STATUS_CHANGE",
"expiresAt": 0
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | {Unique Notification ID} |
type | string | INTEGRATION_STATUS_CHANGE |
Full schema: 3 fields.
From LinkedIn docs
-
Content type
application/json
DELETE_PROSPECT_NOTE
documented from LinkedIn docs (example)
DELETE_PROSPECT_NOTE Recruiter prospect note is deleted
Identified by type field in the body; leadAction or action says what happened
Resource talent
{
"prospectNoteId": "1323073443",
"type": "DELETE_PROSPECT_NOTE",
"integrationContext": "urn:li:contract:123"
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | DELETE_PROSPECT_NOTE |
Full schema: 3 fields.
From LinkedIn docs
-
Content type
application/json
Other LinkedIn events
LEAD_ACTION
documented official schema
LEAD_ACTION Lead form response is created or deleted
Identified by type field in the body; leadAction or action says what happened
{
"type": "LEAD_ACTION",
"leadGenFormResponse": "urn:li:leadGenFormResponse:1a2b3c-4",
"leadGenForm": "urn:li:versionedLeadGenForm:(urn:li:leadGenForm:1, 1)",
"owner": { … },
"associatedEntity": { … },
"leadType": "EVENT",
"leadAction": "CREATED",
"occurredAt": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | LEAD_ACTION |
Full schema: 10 fields.
From LinkedIn docs
-
Content type
application/json
ORGANIZATION_SOCIAL_ACTION_NOTIFICATIONS
documented from LinkedIn docs (example)
ORGANIZATION_SOCIAL_ACTION_NOTIFICATIONS Likes, comments, shares or mentions on a Company Page
Identified by type field in the body; leadAction or action says what happened
{
"type": "ORGANIZATION_SOCIAL_ACTION_NOTIFICATIONS",
"notifications": [ … ]
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | ORGANIZATION_SOCIAL_ACTION_NOTIFICATIONS |
Full schema: 23 fields.
From LinkedIn docs
-
Content type
application/json
Route LinkedIn events by type.
Event Gateway receives every LinkedIn delivery and filters and routes it by event type, so each service gets only the events it handles.