Building with linked_in_api
Download as KEY, PPTX1 like555 views
The document discusses using the LinkedIn API for building applications. It provides an overview of the JavaScript and REST APIs, noting that the JavaScript API is easier to use but more limited while the REST API provides more flexibility but requires more development effort. Both APIs require user authorization. The document then describes some of the capabilities of the LinkedIn API, such as accessing profile and connection data, performing faceted people searches, and accessing jobs and group data. It also outlines some rules for using the API related to data storage and exposure.
![From Curiosity to ROI — Cost-Benefit Analysis of Agentic Automation [3/6]](https://cdn.slidesharecdn.com/ss_thumbnails/session-3-250903141006-a3917e1a-thumbnail.jpg?width=560&fit=bounds)
Building with linked_in_api
- 1. BUILDING WITH LINKEDIN API Pains, constraints and data
- 2. JUST READ THE http://
- 3. BORING STUFF Request API Keys (You want 2
- 4. 2 APIS Javascript and Rest
- 5. JAVASCRIPT API • Easier to respect • Good the TOS ;-) • Comeswith templates and • Less good tags • Client-side
- 6. REST API • Good • Less good • Server-side • Need to know the API • Need to build everything
- 7. BEST OF BOTH You can exchange token from an API to the other says Sarah.
- 8. REQUIRES USER AUTH You can only call the API through an
- 9. POWER TO THE API • Profile API: Standard vs Public • Profile fields: So many it’s insane. • Connections API: Usually way enough info. • People Search: The Power of facets. • Groups API, Social stream, Invitation (friend-only) • Jobs API: Bookmarks and suggestions.
- 10. NO EMAILS E-mail addresses are never exposed
- 11. PLAY BY THE HOFFMAN RULES • NoLinkedIn data can be stored (except profiles if explicit) • Data from one user's LinkedIn account/network may not be exposed to another user • Youcannot use the APIs in conjunction with data scraped by you or other third parties from LinkedIn
- 12. FACETS http://api.linkedin.com/v1/people-search:(facets:(code,buckets: (code,name)))?facets=location <people-search> <facets total="1"> <facet> <name>Location</name> <code>location</code> <buckets total="5"> <bucket> <name>United States</name> <code>us:0</code> </bucket> <bucket> <name>San Francisco Bay Area</name> <code>us:84</code> </bucket> <bucket> <name>France</name> <code>fr:0</code> </bucket> ... </buckets> </facet>
- 13. LIST OF FACETS • Location • Industry • Network • Language • Current company • Past company • School
- 14. FACETED SEARCH • http://api.linkedin.com/v1/people-search:(facets:(code,buckets: (code,name,count)))? facets=location,network&facet=location,us: 84&facet=network,F
- 16. TIPS • Read the TOS • Read the docs • Expect weird return type (private??) • Expect undocumented errors • Monitor your usage
- 17. ANY QUESTIONS? My email is