Retrieve LinkedIn Lead Gen Form responses via the Lead Sync API
domain: learn.microsoft.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Apply separately for Lead Sync API access — access to the standard Advertising API does not automatically grant this program.
Once approved, authenticate with an OAuth 2.0 bearer token carrying r_marketing_leadgen_automation (to read forms/responses) and rw_ads (to manage Lead Gen Forms) scopes.
Call the leadForms resource to look up existing Lead Gen Forms associated with the organization or ad account.
Call the leadFormResponses resource to fetch submitted responses for a single form response, multiple form responses, or all responses at the organization level.
On integration setup, perform a one-time full pull of historical leadFormResponses to avoid missing leads submitted before the sync was wired up, then poll incrementally going forward.
Known gotchas
LinkedIn only retains lead form response data for up to 365 days — a sync gap longer than that permanently loses older leads.
Lead Sync API access is a distinct, separately-approved program from both the Marketing Developer Platform and Matched Audiences access — expect a separate application.
The REST API base is https://api.linkedin.com/rest and requires a pinned LinkedIn-Version header; omitting or mismatching it can break requests in confusing ways.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?