Those are similar to Facebook Social Plugins, but it does not mean their API library is functional yet.

First issue with LinkedIn API is they require SSL (HTTPS), but they do not serve you the API in HTTPS; this means you've mixed content 24/7, which makes absolutely no sense.

Second issue is their JS and PHP API does not communicate very well. Just recently at my request was it implemented to communicate with one another, but it's not stable resulting in Cookie being lost on ever page load, which makes it worthless.

You're welcome to attempt to hack it in, but it will take massive knowledge of their API and complete understanding of how CB Connect/FBC/TC works.

I'll be reviewing LinkedIn implementation likely around June giving the API ample time to mature. During this time I remain in contact with LinkedIn and continue testing until API meets our standards and stable usage. As is it is too limited as to how can use it (requires SSL) and how developers can implement it (2 APIs, but don't communicate well).