Note that there are some explanatory texts on larger screens.

plurals
  1. POLinkedin API: Looking for the most effective way to search a large list of people
    primarykey
    data
    text
    <p>I'm trying to find the most optimal way to search a list of names in LinkedIn. For example if one has a list of 150 peoples and not to hit the throttle limit of 100, the requests must be combined somehow. So far I have come up with the following syntax using the JavaScript API: </p> <pre><code>IN.API.PeopleSearch() .fields("id", "first-name", "last-name", "positions", ...) .params({ "first-name": firstname1 OR firstname2 OR firstname3, "last-name": lastname1 OR lastname2 OR lastname3 ... }) </code></pre> <p>Which works, in a way, but with this search, following problems arise:</p> <ol> <li>"John Smith" and "Juan Carlos" would also return "John Carlos" and "Juan Smith". Which means that the response is getting larger and larger with more names searched at a time and needs more requests to get the whole list of results. This data also needs to be processed to filter out undesirable results. Which is not a problem, but could use unnecessary amount of requests if there is a better solution.</li> <li>Because of the first problem the people should be searched by a group of some reasonable amount - somewhere let's say 3-10 people.</li> </ol> <p>With a list of 150 people my current solution would probably be enough, but in case something goes wrong and the same list needs to be searched again, then the limit would probably be already reached and it's not possible to search the same list again before tomorrow.</p> <p>Is there a better solution, that I haven't found yet, to optimise the number of requests?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload