The blog of the Budapest based Digital Natives covers the topics such as technological challenges we meet in our work, also our solutions and developments related mostly to Ruby on Rails and e. g. JavaScript. You can read about project management methodologies, which drive our workflow, such as agile or scrum. We don’t forget to report about our work and free-time related events and activities.



2011 (1) 2012 (4) 2013 (5) 2014 (1) agency (1) agile (1) agilis (13) android (1) angel (2) anita (2) API (1) árazás (2) artisjus (1) balaton (1) bécs (1) becs (1) becslés (1) befekteto (1) befektető (7) bemutatkozás (1) berlin (1) beszédfelismerés (2) beszédtechnológia (1) bitbucket (1) borkóstoló (1) budapest.rb (1) célok (1) client (4) cloud (1) code hulk (1) coding (1) coin (1) concept (2) conference (1) continuous integration (1) cross browser (1) cross platform (2) csapat (4) csapatépítés (1) csocsó (1) David (1) ddb (1) deployment (3) design (2) dev (4) dev meeting (2) digital (1) diktálás (1) dojo (1) ebook (1) education (1) elemzés (3) elmélet (1) english (8) English (1) értékelés (1) értékesítés (3) extreme programming (1) fejlesztő (3) feliratozás (1) Friday (1) frontend (2) game (3) game of thrones (1) gerzson (2) hackfwd (2) heroku (1) hirdetés (1) hosting (1) icatapult (2) idcee (4) idea (1) implementation (2) inkubáció (9) ios (1) javascript (1) jenkins (1) jogdíj (1) kaizen (1) kalandpark (1) kanban (3) képzés (2) kijev (1) kipuedu (1) kirándulás (1) kocákzati tőkealap (1) kommunikáció (1) lean (2) LinkedIn (1) Logidok (1) mahasz (1) meetup (9) mindroom (2) Mitnick (1) mixgar (14) mobil (4) MVP (1) mvp (2) nabaztag (1) natives (1) olasz (1) open source (1) people search (1) piknik (1) planning (1) playertise (3) prága (1) presentation (1) product owner (1) product roadmap (1) project (1) prototípus (1) prototype (1) rabbit (1) rails (15) ruby (13) rupy (1) scrum (9) search API (1) series (2) sharewood (1) siker (2) sorozat (1) spaceship (1) speedinvest (1) startup (6) startup week (1) String (1) szerződés (1) szolgáltatás (2) taxi (3) taxitrust (3) taxtrust (1) techshow (2) testing (2) teszt (1) titanium (1) toborzás (2) tőke (2) toptal (1) trónok harca (1) ügyfél (1) UI (1) UML (1) UX (2) üzletiangyal (1) vagrant (1) varga anita (1) verseny (2) videó (1) videóarchívum (1) vienna (1) világhírnév (8) virtualbox (1) vm (1) vodka (1) web (8) wired (2) workflow (2) XP (1) xp (3) Címkefelhő

In one of our recent projects, we had the opportunity to work with the LinkedIn People Search API. Using LinkedIn for signing in is becoming more and more popular these days, but in this project, the Client wanted us write an application which is able to perform people searches.

In this post, we want to share what we learned about the possibilities and limitations of the API for non-technical people that are or may be planning to use the API.


Intended use

The first thing you have to do is make sure that the intended use of application does not violate LinkedIn’s Terms and Conditions. Think over what the application is for, who the target audience is, and whether these are in accordance with the People Search API documentation which states that:

  • “It may not be used for the purposes of database matching, candidate sourcing, or lead generation without an established business relationship with LinkedIn. For information on partnership opportunities, and how to apply, visit our Partner Programs page.

  • Search results may not be stored or offered as aggregated search.

  • All API calls must be made within an active user session.

  • You cannot let multiple people search using the authentication credentials of one person. Each person must authenticate individually.”

Only if you feel confident that your application can comply with these terms should development start. We do our best to warn clients of the possibility of having an application banned, but we are not legal experts, and do not take responsibility for developing an application that is determined to be violating T&C.

The second restriction you should be aware of is that People Search API is available only for logged in users, and only within the 1st and 2nd degree connections of the logged in user. It means that the API will search only in the 1st and 2nd degree connections of the user. Searching for “out of network” people that are not either 1st or 2nd degree connections is possible only if the search query includes both the first and last name of the person. So you must exactly know whom you are looking for.

People Search API throttle limits

LinkedIn sets strict throttle limits for Search API calls. Only 100 results will be provided for each search and 10 results will be displayed per page. Displaying each page is considered one API call.

Your application can have 100K calls per day, but individual users will have only 100 calls per day (400 for developers). The counter resets at 24:00 every day. A developer working on the app could easily reach that limit early in the day and not be able to perform another search before midnight.

Though there is an option to buy different Premium Plans which can give you more options as a LinkedIn user, on the official developer forum about the API permission model, it says that The level of account you have with LinkedIn doesn't affect what you can do as far as API queries go.”” (source)


Without going into too many technological details, we would like to briefly point out some of the benefits of using Ruby on Rails for a project like this.

The fun part about being a Rails developer is when you’re integrating with a service that is basically guaranteed to have some 3rd party library (or gem) that take care of part of your work for you. For the people search API, we used the gem called linkedin (, and for the LinkedIn sign-in process we chose the omniauth-linkedin gem ( as an extension for the famous devise user management library.

Using gems like these will ensure that your developers don’t have to reinvent the wheel, and the implemented solution will be constantly tested and upgraded by the open-source community of Ruby developers.




LinkedIn has built a great professional network, and it is natural that they want to protect the greatest value of the site. So if you can accept the limitations and restrictions of the People Search API, it can be a useful additional add-on or feature for your application.

However if you are planning to use the API heavily with use cases that include people search as a main feature, then we would recommend first establishing an agreement with LinkedIn before risking getting your app banned. :)

Címkék: ruby English API LinkedIn people search search API

Szólj hozzá!

A bejegyzés trackback címe:


A hozzászólások a vonatkozó jogszabályok  értelmében felhasználói tartalomnak minősülnek, értük a szolgáltatás technikai  üzemeltetője semmilyen felelősséget nem vállal, azokat nem ellenőrzi. Kifogás esetén forduljon a blog szerkesztőjéhez. Részletek a  Felhasználási feltételekben és az adatvédelmi tájékoztatóban.

Nincsenek hozzászólások.