forked from mrgaaron/LinkedIn-Client-Library
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README.txt
48 lines (31 loc) · 1.96 KB
/
README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
This branch now includes a fair number of pull requests from PhilGo20 to help with the updates LinkedIn made to their search API, as well as some minor bug fixes.
Big thanks go out to Phil for helping out!
See the docs here:
http://developer.linkedin.com/docs/DOC-1191#
Here's an example of how to use the search:
from liclient import LinkedInAPI
api = LinkedInAPI(API_KEY, SECRET_KEY)
params = {'first-name': 'John', 'last-name': 'Smith'}
field_selector_string = '(people:(id,first-name,last-name,headline,public-profile-url),num-results)'
results = api.search(ACCESS_TOKEN, params, field_selector_string)
# do stuff with results
Dependencies:
lxml
httplib2 (for OAuth)
Installable via:
python setup.py install
To get started:
1. First, of course, we need to instantiate the API object with our consumer key and secret:
consumer_key = 'mykey'
consumer_secret = 'mysecret'
APIClient = LinkedInAPI(consumer_key, consumer_secret)
2. The first step for a new user is to retrieve a request token. This is done like so:
request_token = APIClient.get_request_token()
3. Then, we generate the URL to send the user to for authentication (I know the first line is a little ugly, I will probably simplify this soon):
authorization_url = APIClient.base_url + APIClient.authorize_path
url = "%s?oauth_token=%s" % (authorization_url, request_token['oauth_token'])
4. Once the user has authenticated, you will need to collect the oauth_verifier returned by the LinkedIn server in the URL. This can be done
either by having the user type it in themselves or collecting the URL argument on the redirect from LinkedIn. However you decided to get it,
this is how you use it:
access_token = APIClient.get_access_token(request_token, oauth_verifier)
That's it! You can use this access token for every request this particular user makes, for as long as they have authorized you to use it.