api « Pocket Blog

Posts Tagged ‘api’

Introducing the New Pocket API for Developers and Publishers

November 7th, 2012 • By Mark

It has been an incredible year for Pocket: We’ve grown to more than 6 million users, and we’ve expanded to new platforms including Mac, Chrome and Safari, in addition to our iOS, Android and Kindle Fire apps.

But we couldn’t have done it without you. We now have 10,000 developers integrating their apps and sites with Pocket, and 45% of Pocket’s more than 1 million daily saves come from third-party apps.

“Save to Pocket” is now a core part of the user experience inside the most popular apps and websites—from Twitter and Flipboard to Tweetbot, Digg, BuzzFeed and more. And in content-focused apps like Zite, Pocket is often one of the most-used share services, alongside Twitter and Facebook.

Today we’re introducing the new Pocket API, which makes it even easier for developers and publishers to put Pocket to work in their own apps—and to do so in more powerful ways.

Start Building with the New Pocket API

What’s In the Pocket API

Our new API includes easy integration and access to the great Pocket features available in our native apps. Here’s what’s new:

• Quick authentication: With OAuth 2, users can connect to Pocket with just two taps and without having to enter their username and password.
• Drop-in iOS/Mac SDK: With just a few lines of code, you can drop Pocket’s all new Objective-C SDK into your app, which manages authentication, performs API requests, and provides access to all of the new API features. (See our video demo below.)
• New API Features: Developers and publishers can access all of Pocket’s most up-to-date features, including favorites, content type filters, more robust tagging, and domain searches.
• New developer portal: We have a new developer site with improved documentation including step-by-step implementation instructions and examples.

What Developers Are Saying About the Pocket API

“‘Save for later’ has become an essential part of mobile news consumption, and I wouldn’t even consider launching a news app without Pocket integration.” -Mike Klaas, co-founder, Zite

“Pocket integration continues to be one of most asked-for features in the new Digg, and the new SDK made implementation super easy!” -Jake Levine, general manager, Digg

“Saving articles to Pocket is a must-have feature for a content-driven application like Readingly. And Pocket users are some of the most engaged users we have.” -Alex Kristofcak, founder, Readingly

“Save-for-later support is an important feature for TweetCaster, which makes integrating with Pocket essential. From a development perspective the new API and iOS SDK couldn’t have been easier to implement and we think our users will appreciate how seamless the integration is.” -Evan Conway, president of OneLouder Apps

Get Started Now

Developers can get started immediately with the Pocket API: Just sign up here and start building.

More Resources: Pocket SDK Demo

Pocket Objective-C SDK Screencast from Pocket on Vimeo.

Posted in News , api, developers, Pocket, publishers, sdk

On Twitter’s New API Guidelines and Pocket Integration

August 17th, 2012 • By Nate

We’ve received a number of questions from users and our own developer community about Twitter’s new API guidelines and how it affects use of Pocket with Twitter.

Specifically, we wanted to clarify questions around the following rule in Twitter’s new Display Guidelines:

b. No other social or 3rd party actions may be attached to a Tweet.

We have a strong relationship with Twitter so we reached out to their team for further clarification. We’ve been told that the new API guidelines are not intended to affect or hamper your ability to integrate Pocket with Twitter apps or clients. The ‘social actions’ refer to Twitter’s own actions like Fav, RT, and Reply.

Your Pocket integration with Twitter and third party clients will continue to work like normal. As always, we’ll continue to keep our developers and users in the loop.

p.s. If you want to test that saving works just to be sure, you can always try saving any of the content from @PocketHits!

Posted in News , api, developers, Pocket, twitter

Pocket Works with Your Old Read It Later Account (and All the Apps that Support It)

April 18th, 2012 • By Mark

Yesterday was a big day for Read It Later—now Pocket—and we are humbled by the community’s response to our new version, look and name.

There have been a few questions from current users about the change, so we wanted to clarify what’s changing, and what’s not:

1. Use your existing Read It Later account credentials to log in to Pocket

If you’re already a Read It Later user, you can use your exact same username and password to sign in to Pocket. Once you’re signed in, the new Pocket apps will have all the same content you previously added to your queue.

2. No need to set up your apps again

Pocket still works with all the 300+ apps that support Read It Later—including Twitter, Flipboard, Zite and more. If you already integrated Read It Later with them in the past, you’re set. (Many apps will still have the old Read It Later name and logo, but that integration still works seamlessly with Pocket.)

3. No need to add a new bookmarklet or extension

The old Read It Later bookmarklet and extensions work with Pocket! The name will even update itself. (Chrome users, you can also try our new extension.)

For the Pocket iOS app, you can still add the mobile bookmarklet by going to Help -> How to Save inside the app.

4. Read It Later’s API is completely supported by Pocket.

If you’re a developer or publisher with Read It Later API integration or embedded “read it later” buttons, nothing will break, and everything will work seamlessly with Pocket. (You’ll probably just want to update the name and logo at some point. We’ll provide more resources for that soon.)

As always, we’re on hand at help.getpocket.com or at @PocketSupport to answer any other questions you might have.

Posted in News , account, api, apps, Pocket, Read It Later, support

Pocket