LinkedIn API
GET /adFormResponses endpoint removal
Stopped workingSubscribe to LinkedIn APIShare
Calls to GET /adFormResponses on LinkedIn API stopped working on July 31, 2025.
Calls it hits
GET /adFormResponses
What to use instead of these calls
Developers must migrate using the migration guide.
In LinkedIn API's words
Legacy endpoints that will be sunset include: `/adForms`, `/adFormResponses`, `/leadNotificationUrls`.
Facts
- API
- LinkedIn API
api.linkedin.com - Kind
- Endpoint removal
- Takes effect
- July 31, 2025
- Calls after that day
- Fail
- Source
- Changelog
- Last updated
- Verified
- , against LinkedIn API's own pages
Questions
When does this change take effect?
Calls to GET /adFormResponses on LinkedIn API stopped working on July 31, 2025.
What happens to calls after July 31, 2025?
They have failed since July 31, 2025.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from LinkedIn API 10
-
/202306/*Version retirement Stopped working -
/202307/*Version retirement Stopped working -
/202401/*Version retirement Stopped working -
/202402/*Version retirement Stopped working -
/202403/*Version retirement Stopped working -
/202404/*Version retirement Stopped working -
/202405/*Version retirement Stopped working -
GET /adFormsEndpoint removal Stopped working -
GET /leadNotificationUrlsEndpoint removal Stopped working -
POST /media/uploadEndpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.