Skip to content

LinkedIn APIs: Professional networks via REST

LinkedIn, the professional networking site of choice, has been very busy lately introducing new features.  You may have seen the news about their “InMaps” showing connectivity to, and clustering of, members of your network.  And perhaps you’ve tried out their Skills searches or their LinkedIn Today daily view of the news that matters to others in your network.

But did you know they also support third party development with a RESTful developer API and embeddable widgets you can use in your applications?  LinkedIn is also previewing a JavaScript API (currently in early access) to make using the REST API along with login and sharing buttons easy to do for browser-based applications.  Let’s look at the REST API first.

The API provides access to the following resources:  Profile, Connections, Search, Messaging, and Network Updates including member updates, shares, comments, and likes.  The LinkedIn API Resource Map provides example calls for each of these resources; click here to access it.

One convenient way to try out the LinkedIn APIs is to use the Apigee LinkedIn API Console.  For instance, to make a network updates (read: “feed items”) call, you would load the console and then click on “Network Updates“, then under that “people/~/network/updates“.  Click on the padlock to the immediate left of the API call box, then select “OAuth” for authentication:LinkedIn OAuth sign-in prompt

Click to read the complete post on the PayPal X Developer Network including the rest of the authentication and API call execution steps.

March madness

My NCAA teams failed to make it through last month, but there was still a lot of madness for me on the payments-related front.  Here’s my mad monthly recap.

I published the first two parts of a four part series on “Selling Digital Goods in Data Markets”.  Part 1 focuses upon the early movers and innovators, including a look at features I think are very desirable in a data market.  Part 2 discusses selecting a data market and dives deeper into Factual and Infochimps, including how to use Infochimps’ Twitter influence metrics API via YQL.  Source code for the Python example is available on GitHub (click here).

https://www.x.com/servlet/JiveServlet/downloadBody/3337-102-2-3718/03162011_article_007.png

Watch for the third and fourth parts of this series to publish to the DevZone soon.

I also wrote the following DevZone blog posts last month:

Click to read the complete post on the PayPal X Developer Network including links to other important news and information for developers.

Notes from the week of 2011-04-03

PayPal X Platform

Big data

Wireless and mobility

APIs and development

Personal things

  • Note to self: Colorado GMU 75/751 map http://bit.ly/hC5X8V #
  • Hunters: Nikon "Spot On" ballistics software http://bit.ly/dUl0tU generates free printable hold charts for your scope/ammo/zero combo #
  • Internet connectivity issues since last night, with deadlines of course. Argh, Cox! #
  • Generate your own Colorado GMU maps http://bit.ly/fyX1Ak via the CO Division of Wildlife #

Amazon Appstore

Twitter APIs: Hacking tools

In my last post I introduced the Twitter REST APIs while sprinkling in a bit of history and providing some information on using Twitter’s Twurl console.

This time I want to highlight some additional development tools to help you be productive programming against Twitter’s APIs.  Let’s take a whirlwind tour through hacking Twitter with Apigee’s Twitter console, YQL, Infochimps, and GNIP technologies.

First up, Apigee’s Twitter console.  This is similar to the Apigee PayPal and Facebook consoles I’ve written about here before.  Apigee’s consoles make API exploration, learning, and call prototyping a quick and easy thing to do.  Their Twitter console is a great way to start using the Twitter API immediately, similarly to using Twurl.  But if you learn how to use Apigee’s console, you can take the same generalized skills over to other Apigee provided consoles including the PayPal console mentioned above.  It’s worth the little bit of time required to get up to speed, in my opinion.  Click here to try it out for yourself.

I’ve written a lot about YQL and Infochimps recently, including a how-to on using Infochimps’ Twitter influence metrics API via YQL.  YQL allows you to use SQL-like queries to access a wide variety of web APIs including Twitter’s, while Infochimps provides a number of Twitter stream and data related datasets via their data market.  I’d encourage you to read my previous posts and articles on both subjects to see how you can use them in your Twitter development.

Click here to read the full article on the PayPal X Developer Network including information on drinking from GNIP-provided Twitter firehose streams and a fantastic O’Reilly book that will give you recipes for hacking on Twitter data.

Twitter APIs: Getting started with the RESTful interface

I’m writing an ongoing series of posts on Mobile, Social, and Local technologies, collectively “MoSoLo“.  Previously I’ve covered the rise of web APIs, Facebook (history and openess, social plugins, Open Graph, and the Graph API), web API power tools for programming bliss including YQL for PayPal transactions, data markets, REST+JSON, and more.

In this post I’m going to start exploring the power of 140 little characters at a time:  Twitter and its APIs.  I’m going to assume you’re familiar with the basic Twitter service and the company behind it; if not, please read through the Twitter Wikipedia page and “A Brief History of Twitter” for background.

By the way if you’re curious as to why Twitter messages (“tweets”) are limited to 140 characters, read “How Twitter Was Born” for the details.  The short answer: wireless texting (SMS) limitations, as the service was heavily SMS-oriented in its early days.

Though Twitter has done some things of late that have the developer community and its partners up in arms, it nonetheless has one of the most used RESTful APIs on the web.  You can learn from Twitter’s API even if you don’t want to go down the path of partnering with them.

Twitter’s API is explained on their API Documentation page.  It includes sections on authenticating using OAuth, a slideshow introducing the Twitter API (@twitterapi), a description of the main Twitter REST API used to access core data including timelines and user information,  Twitter Streaming API documentation (this API is used to access near realtime subsets of public Twitter status updates), and information on the RESTful search API that came to Twitter via their acquisition of Summize.

Note that Twitter has chosen the one true web path:  REST + JSON +OAuth.  This is a very good thing for developers as it helps to make the API simple and easy to use.  For instance, to request the 20 most recent status updates (tweets) from the currently authenticated user, you would make the following HTTP GET request:

http://api.twitter.com/version/statuses/user_timeline.format

where format specifies which format you’d like to receive results back in (options include json, xml, rss, or atom) and version specifies the API version for the call.  Click here to load this call with JSON response into Twitter’s “Twurl” API console, then click “Send” to see the results for your own authenticated account (you will need a Twitter account for this to work).

Click here to read the full post on the PayPal X Developer Network including another example of the Twitter REST API’s usage.

Notes from the week of 2011-03-27

#Winning with JSON

PayPal X Platform

Big data

Wireless and mobility

APIs and development

Personal things

Running

Amazon Appstore launches, encourages QR code links

Amazon has launched their Android application store (aka “Amazon Appstore”) in the US.

http://amazonappstoredev.typepad.com/.a/6a0148c71fb71b970c014e86e16089970d-pi

Amazon promises to “make it easy to find, discover and buy Android apps”.  This is a not-so-slight jab at Google’s Android Market, known for being, shall we say, less than optimal in surfacing the best and most interesting apps.  Amazon’s announcement notes:

We are offering a few unique features such as recommendations based on customers’ browse and purchase history.  This is one of the automated marketing features we discussed previously.   Automated marketing includes placements in search results, browse based results, bestsellers, and more.

Amazon also mentions their Appstore Developer Portal reporting features.  The screenshot they provide (see below) shows basic albeit important information on how well your apps are selling, though it would have been great if they’d shown something with more data in it (don’t advertize you’re new with empty screenshots in the future, guys!).

http://amazonappstoredev.typepad.com/.a/6a0148c71fb71b970c0147e36136f9970b-800wi

Click here to read the complete post on the PayPal X Developer Network including a info on Amazon’s encouraging developers to link to their Appstore entries with QR codes and a link for more on Apple’s suing Amazon over the name of their market.

O'Reilly books and PayPal donations to help the Japanese people

This post is a bit of an aside from my usual payments and programming fodder, but I think it’s worthwhile to get the message out since there are some time limits on special O’Reilly and PayPal offers that you may be interested in that benefit Japanese disaster relief.

The first offer:  Today’s O’Reilly ebook and video “Deal of the Day” is good for 50% off ebooks and videos, plus all of the proceeds (less author royalties) go to the Japanese Red Cross Society to help in relief efforts.  Just shop the O’Reilly store and then use discount code “DDJPN” during the checkout process to save money while at the same time donating to help the Japanese people.

The O’Reilly site notes that they’ve hit $50,000 USD of donations as of 9AM Pacific time.  They are hoping for $200,000 USD by the end of the day.  This is a great way to pick up a book or video (or several of each!) that you’ve been wanting while helping out.

Similarly, PayPal is crediting transaction fees for donations to a number of charities providing assistance to the Japanese people as they recover from the recent disasters.  PayPal will continue crediting these fees through April 10th.  If you are in the US you can see a list of available charities by clicking here; if in Canada, you can donate to the Canadian Red Cross here.

Read the complete post on the PayPal X Developer Network.

Notes from the week of 2011-03-20

PayPal X Platform

Big data

  • Quora: What underlying technologies are used to implement the major data markets? Answer: http://qr.ae/i6UX #

APIs and development

Personal things

Running

Infochimps Twitter influence metrics screenshot

REST + JSON = #winning!

I’ve written a lot of late about REST and JSON.  I hold them dear as being two pillars at the center of good web API design and data delivery.

So I was delighted to read two nice posts on these matters recently on Apigee’s “API Best Practices and Infrastructure” blog.

The first, “REST API design for SQL programmers“, is actually a short slide presentation (accessible via Slideshare here).  It walks you through designing a well thought out, simple, easy to use web API when you’re used to thinking in SQL.  Apigee CTO Greg Brail (@gbrail) uses an employee database example to show you how to design a RESTful API to access, add, and remove employee data.  This presentation is recommended for anyone getting up to speed with REST or especially for someone designing a RESTful API for the first time.  Simple and concise, just as it should be.

The second, “Not serving JSON AND JSONP? Then you’re doing it wrong!“, is a blog post from Mr. Brail explaining why we’re seeing such a tremendous rise in JSON and the related JSONP.  In a nutshell, this approach leads to smaller messages being sent across the network, very important for anyone doing mobile work.  Because JSON is less complicated than many alternatives, this approach often also results in faster parsing and manipulation of the message contents.

Click to read the complete post via the PayPal X Developer Network. Your comments there would be greatly appreciated.

Design a site like this with WordPress.com
Get started