New York Times APIs

http://developer.nytimes.com/docs

by raldu • 12 years ago

183 31 12 years ago

developer.nytimes.com

mark_l_watson• 12 years ago

I occasionally use about three of their APIs. Really good stuff.

Take a look at the semantic API that provides NYT's controlled vocabulary for entities.

xiepie• 12 years ago

Newswire API has great potential! It would be a good resource for creating alerts for specific type of news.

jfiore3• 12 years ago

IFTTT did just that, and more, to create a number of the triggers in the NYTimes channel (all powered by our public APIs)

https://ifttt.com/nytimes

flocial2• 12 years ago

From their FAQ:

11. What do you mean by "commercial purposes"? Here are a few examples of what we consider commercial purposes:

1. Selling New York Times content or data in any application. 2. Charging a subscription fee for any New York Times content or data. 3. Selling any application built with one of our APIs.

If you are making more than 5,000 calls per day (via an application or any other method) to an individual API, we will notice that and assume you're using our API for a commercial purpose. Please contact us if you have hit that limit but do not think you are using the API for a commercial purpose.

---------

It looks enticing but I'm not entirely sure if these limitations negate the purpose of the API existing (aside from internal use and hobbyists using it for personal purposes).

boise• 12 years ago

What do view as the purpose of the API existing?

flocial2• 12 years ago

It just seems like a blanket ban on any commercial applications without some kind of payment and a very small request limit (5000), limits people who will even consider experimenting with it. It seems more geared for web applications/sites that have no native phone apps.

cowsandmilk• 12 years ago

(a) I've used it for academic research (b) Does not seem to exclude use in an open source application or freeware. (c) They tell you to e-mail them if you want to use it commercially. They have a documented API you can play with, then if you want to make a commercial product, you can pay them and use the same api that you are already familiar with and understand the capabilities of.

marban• 12 years ago

What's new about it? Just saw I have an app there that dates back to 2008.

maxharlow• 12 years ago

The Guardian also has an API: http://explorer.content.guardianapis.com/

jawerty• 12 years ago

This is really cool. I think these news APIs are really under appreciated

naturalethic• 12 years ago

setLimitsPublicDiscourse() worshipGovernment() provideIntellectualLeftistAirOfAuthority() makeBrokenWindowFallacy() scrambleToStayRelevant() winPulitzerAndOrNobel()

stefan_kendall3• 12 years ago

I've seen a lot of broken window fallacy recently. I've heard it a lot in the past few days, mostly with respect to Syria.

jasonmoo• 12 years ago

It's a pretty nice set of apis. I wrote an app that overlays the events feed onto google maps for geo eventin goodness.

http://nyevent.in

Source: https://github.com/jasonmoo/eventin

ww520• 12 years ago

What is the pricing structure once exceeded the daily call limit?

jjallen• 12 years ago

They don't tell you what the limit is:

"12. Is there an API call limit? When you register for an API key, you'll receive information about limits and other Terms of Use. If you approach a limit, a warning e-mail will automatically be sent to you."

http://developer.nytimes.com/docs/faq#6

jfiore3• 12 years ago

It varies by API, and is specified when you register for keys.

rodrigoavie• 12 years ago

Nice, what abou a Ruby wrapper for this API? Like this https://github.com/rodrigoalvesvieira/NYTimesAPI

chatmasta• 12 years ago

We're living in an exciting time for the media industry. Traditional companies, with their origins in paper-based news distribution, have no choice but to change their business models. The content supply chain, fundamentally, must look something like this:

NYT[ journal -> write -> edit -> publish -> distribute]

Content has to be produced, and it has to be distributed. In general, any piece of content will flow along that chain.

Before the Internet, the "old guard" of media -- The Times, The Post, etc. -- held a monopoly on the entire supply chain. They found the sources, wrote the articles, and even delivered them to your door, printed and ready to read. It would have been difficult for an outside company, or industry, to encroach on any part of the NYT business. Why would the NYT surrender part of such a valuable supply chain? By controlling content from production to distribution, they were able to charge higher prices for it.

But now, the distributive power of the Internet has broken the supply chain in half, resulting in new economic specialization. Buzzfeed beats the NYT in distribution, but the NYT beats Buzzfeed in production quality. Now, the supply chain looks more like:

NYT[ journal -> write -> edit -> publish] -> [distribute]BUZZ

It seems that there is a place for both Buzzfeed and the NYT on the supply chain. One can control, and should specialize in, the production of content. The other can distribute it.

Old media companies are finally "waking up" to the threat of content distribution experts like Buzzfeed. The Guardian, WaPo, and the NYT have fantastic tech departments forming a smart digital strategy. They recognize that yes, Buzzfeed is taking part of their supply chain, but no, Buzzfeed cannot compete with the NYT on journalistic integrity. As long as the NYT employs the staff that it does, with writers of decades of experience and connections in the industries they cover, there will be a demand for NYT content. Some of that demand may come from end-consumers, and some may come from distribution companies like Buzzfeed. But the fact of the matter is, the NYT can still own the production part of the supply chain, and it makes sense to mitigate the threat to their distribution models by selling production "wholesale" to distributors.

This move from the NYT is a great milestone for their digital strategy. They're recognizing that content, like any product, has a supply chain and production process. They know they own the production process, but the Internet has enabled new companies to own downstream parts of the supply chain. So by releasing API's to their raw content, they are providing access to their raw product for any company who might want to sell it.

leephillips• 12 years ago

I don't recognize your traditional supply chain. It doesn't seem to account for the realities of independent distribution companies, freelancers, stringers, syndication, .....

superuser22• 12 years ago

NYT[ journal -> write -> edit -> publish -> distribute]

That's not how print works. Many papers own their printing presses, but the output is all sold to one distribution company.

That company handles subscriptions, billing, customer service, and delivery for the newspaper as well as a bunch of local publications unaffiliated with the newspaper's parent company (for example, suburban papers and trade press), in exchange for a cut of revenue. It uses the same branding as the newspaper when interfacing with customers, so the interface is (sort of) seamless, but it is a separate company with separate shareholders.

That's how it's always worked in my hometown, since at least the 80s. So this adjustment might not be that innovative or disruptive.

larrys• 12 years ago

"Many papers own their printing presses"

Ownership of the press is really (in this day and age or even 20 years ago) not that important. There are plenty of web printing houses that would be glad to print your newspaper and use some of their excess capacity. There are (and have always been) many companies that would be willing to distribute that paper if you gave them names of people that want to receive the paper. In fact if you have NYT homes delivery in many cities (outside of NY Metro) it is probably delivered by the same company that delivers the local paper (thrown on your law by the same driver).

The key of course is getting people that want to buy your newspaper. The content and the marketing of the paper.

rickyyean• 12 years ago

If NYT specializes in the production of content, others would have to value their content over others. I think that's part of the problem. The kind of content the NYT produces is not that valuable. Investigative journalism, which is the hardest and most expensive part of what they do, is valued only by a very small number of people.

bdevani2• 12 years ago

I think this comment vastly underestimates the value of something, placing it only within a marketplace context. Investigative journalism, by actual journalists and not bloggers, is a cornerstone of what we need in a society. Otherwise institutions simply continue unchecked.

The API is the same as anything. NYT specializes in content, Google Translate specializes in machine translation of text. You pay for what you need.

We should be able to come up with some pretty cool uses for nyt api considering the insane amt of content it provides access to. the OP is just one.

LeicaLatte• 12 years ago

the API is a great idea.

So I tried signing up for an account. Their on-boarding process - prehistoric. Nope.

bdevani2• 12 years ago

I think it'd be totally worth reaching out to them with recs on how to update the on-boarding process.

jfiore3• 12 years ago

Hi there, I'm on the team responsible for the public APIs -- and we'd absolutely love to hear more :)

Some people love the single sign on (our developer registration is tied to the normal NYTimes.com registration) and some people hate it -- but we're always listening for direct feedback about what's wrong with the process.

aceperry• 12 years ago

Nice, good to see the NY Times adapting to newer technologies.

kewinwang2• 12 years ago

coool

kewinwang2• 12 years ago

coooool

New York Times APIs

Related Stories