Apply for LinkedIn Talent Solutions partner access through the LinkedIn developer program; API access to Apply Connect and Recruiter System Connect requires a signed partner agreement with data handling restrictions.
Configure your ATS job postings to be distributed to LinkedIn and mapped via the Job Posting API (base path https://api.linkedin.com/rest/ as of the 2025 API version) so LinkedIn can match applications back to your requisitions.
Implement the Apply Connect integration to receive candidate applications in real time when a candidate applies via LinkedIn Easy Apply on a synced job posting.
Parse the inbound application payload to extract the candidate profile data (name, contact, LinkedIn profile URN), resume, and the job requisition identifier, then create or match a candidate record in your ATS.
Implement deduplication logic using the LinkedIn profile URN as a stable identifier to avoid creating duplicate candidate records for candidates who apply to multiple roles.
Note that LinkedIn stopped accepting new Apply with LinkedIn (AWLI) partners as of October 1, 2025 — new integrations should use the current supported Apply Connect pathway.
Known gotchas
LinkedIn API access for talent integrations is restricted to approved partners — do not attempt to access candidate data via general LinkedIn API endpoints without a talent partner agreement, as this violates terms of service.
LinkedIn profile data included in apply payloads is subject to strict data use restrictions in the partner agreement; storing or processing this data beyond permitted purposes can result in partnership termination.
The Apply with LinkedIn (AWLI) pathway closed to new partners on October 1, 2025; integrations built on AWLI need to migrate to the current supported mechanism.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp