Retrieve the current user's list of connections
Retrieve a chronological view of a single user's updates
Retrieve updates from across the current user's entire network. This is similar to the timeline view seen on the LinkedIn home page.
Search LinkedIn's database of over 200 million professionals
Retrieve profile data for a LinkedIn member
Perform a raw API query
Though they return different types of data, all the APIs above support a common interface of the following chained methods:
- result(resultCallback, resultScope)
Fires the API call. Invokes the function specified as resultCallback (optionally in the scope of resultScope). If resultScope isn't specified, the window scope is used. If called with no arguments, the call will fire but the result will not be available.
- error(errorCallback, errorScope)
Fires the API call. If an error occurs, errorCallback is invoked with a payload describing the error (optionally in the scope of errorScope). If called with no arguments, the call will fire but the result will not be available.
Can be used to override the method's default action (POST/GET). When an API makes use of the method method, it will be listed in the standard supported methods. methodType is a string for the HTTP action to take.
Can be used to override the method's posted body content. When an API makes use of the body method, it will be listed in the standard supported methods. bodyContent is a URL encoded post string.
Some APIs allow for parameters to be passed as part of a query string, such as count or start. When an API makes use of the params method, it will be listed with the standard supported methods. paramObject is a set of key/value pairs to transmit with the API call. To pass multiple values for the same parameter name, make your value an array instead of a string. (For example: "type": ["SHAR", "APPS"])
In addition to these standard methods, some of the APIs accept parameterization in their constructor which is described below.