linkedin-api: `search_people` endpoint doesn't work anymore

I used this endpoint 2 days ago and it was working correctly, but it seems LinkedIn updated their API, and now instead of using the endpoint /search/blended they use /graphql?variables=.....

When I use search_people I always get a 403 response, is somebody experiencing the same issue?

PS: My cookie session is working properly

About this issue

Original URL
State: open
Created a year ago
Reactions: 5
Comments: 35 (2 by maintainers)

Most upvoted comments

as an update, I think was able to get the mappings right for the new search endpoint. The current tests show that 16/24 tests fail that are all tied to the search function, so I’ll be forking the repo and seeing if I can bring it back up to 24/24.

MoHayat on Jun 3, 2023

I created a draft PR with the changes suggested by @17314642 and @Timur-Gizatullin + a few modifications. The search_people and search_companies endpoint work for me with these changes and the parameters of my use case but I haven’t tested all the other combinations.

Feel free to add any improvements or suggest changes! I might take a look again at it if I get some time and try to do a cleaner fix, if there is one.

ignaciovi on Aug 11, 2023

any news on the LinkedIn Search. It’s very important feature. Thanks for contribution

engahmed1190 on Jul 20, 2023

i found this from linkedin https://github.com/linkedin-developers/linkedin-api-python-client/blob/main/linkedin_api/clients/restli/utils/encoder.py https://github.com/linkedin-developers/linkedin-api-python-client/blob/main/linkedin_api/clients/restli/utils/decoder.py it should help formatting url params and to better understand what each request is doing

DTS-And-Eaglepoint-Funding on Jun 19, 2023

gotcha, was digging through the docs and I wasn’t able to find anything so makes sense, I’ll take a look there

MoHayat on Jun 2, 2023