Where most services hand you a canonical user ID, LinkedIn's API returns a
unique ID for every
[user, app] pair. In practical terms, this means that if
you start prototyping using Singly's default keys and then later switch to your
own, you will see duplicate data when the same real person looks like two
different users. We're thinking about ways to take care of that for you, but in
the meantime, you may want to get your own keys now and
add them to your application.
All of the connections of the user.
Any network updates by or about the user.
All network updates from the user's connections.