RocketReach API
linkedin_ext_url query parameter removal on GET /api/v2/person/lookup
Deprecated, no dateSubscribe to RocketReach APIShare
The query parameter linkedin_ext_url on GET /api/v2/person/lookup has been deprecated without a shutdown date. Calls continuing to rely on this parameter will eventually fail once it is fully removed.
Calls it hits
GET /api/v2/person/lookupquery parameter linkedin_ext_url
What to use instead of these calls
Send the profile URL as linkedin_url instead of linkedin_ext_url.
In RocketReach API's words
linkedin_ext_url deprecated, please use `linkedin_url` instead
Facts
- API
- RocketReach API
api.rocketreach.co - Kind
- Parameter removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against RocketReach API's own pages
Questions
When does this change take effect?
RocketReach API deprecated GET /api/v2/person/lookup, query parameter linkedin_ext_url without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: RocketReach API has not given a shutdown date yet.
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 RocketReach API 1
-
No date
/api/v2/*Parameter removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.