Daylife helps publishers tell a better story. Our platform helps them source, manage, analyze, and compose content in new ways. What could you do if you had access to the world's news, and had a standardized and rational way to get quick responses to rich queries about what’s happening in the world? We wanted to find out so we built this massive backend that analyzes a slew of news content from a variety of sources (including those of a client’s), and exposes it via the Daylife API. (We also have a slew of WYSWIG tools to make the power of the platform accessible to non-developers, but those too are built on the same Daylife API).
We’ve created an enabling technology, and are now letting it loose into the world, so that publishers and content creators and bloggers and developers and everyone can try their hand at developing new experiences around the news, and at extending the experiences of their customers by leveraging news-based content.
With it you can enhance your website (or iPhone or Android or iPad app) with relevant content from around the world.
The Daylife API provides you access to the horsepower in the Daylife platform and lets you:
Deploying the Daylife API requires the same sort of skills that it takes to write a simple interactive application on the web. PHP, RUBY, Java, Cold Fusion, Perl, or .NET level scripting skills are all it takes. It’s a bit heavier than straight HTML, but not crazy complicated.
If you need help, you can ask us. We’ll point you to someone who can work with you to deploy your Daylife API-based solution.
If you’re a commercial client, our direct assistance will be part of the package.
Yes, we offer a whole slew of WSYWIG tools for our commercial clients. Please visit corp.daylife.com.
Yes! And if not, let us know what you’d like to do... we’ll either point you in the right direction, or we’ll build it into the platform. The Daylife API has grown extensively over the past few years, all the result of client feedback.
No. Daylife indexes thousands of quality news oriented publications. Mainstream news sites, authoritative blogs, as well as content from partners like Getty Images, Reuters, and the AP. As a general rule of thumb, our index grows as clients ask us to add certain kinds of material, so if you’d like to see something in there, ask!
You’re sweet for caring about us!
We get paid to make the Daylife API available, at large-scale, under commercial terms. The commercial Daylife API runs on more highly available infrastructure, and is directly and synchronously supported by the Daylife Team. If you're interested in investigating a commercial Daylife API License, contact us.
Also, you'll need to rely on the community and on asynchronous (e-mail and forum) support for the Developer Daylife API.
Yes! Also, and yes!
No, the Daylife API works in English for the time being.
That’s a darned good question.
We can and do reference images via Daylife API calls.
You are allowed to display images for any of the professional imagery providers that you have agreements with.
There are several high-quality sources for which Daylife can grant limited licensed use, provided that you agree to certain restrictions on use and meet certain minimal requirements. Ask us about this if you want to make images part of your application.
Users of the commercial Daylife API have broader rights to redistribute Daylife provided data.
You can create hundreds of thousands of unique, dynamic pages using the Daylife API. But the Daylife API provides data. It's up to you to turn that data into web content for your site or application.
We have an API call article_getRelatedArticles that returns articles from the same story cluster that your article belongs to. However, a lot of times your article might not get clustered with a big story or you want related articles from the past.
In that case, you can use a combination of API calls to get these related articles. Here is how:
If you want to restrict the results only to your publications, you can use the parameters source_whitelist=sourceidA&
You should also use start_time that is 60-80 days in past. The default time period is one month in our APIs.
A great implementation of this is done by our client New York Post. Here is an example of an article from their site- http://www.nypost.com/seven/
Daylife categorizes the topics into following categories:
You can filter the topics returned for all xxx_getRelatedTopics calls by providing these values for the include_topic_type parameter as multiple name-value pairs. E.g.:
You can use topic_getInfo to determine if the query you have is a topic in Daylife or not. If it is, you will get back information about the topic such as the topic_id. If your query is not a topic in Daylife, the API will return you an error code of -2008.
Topics are an ever-growing inventory in Daylife. There are currently the following types of topics returned by Daylife API calls:
In case you have a query and you want to know if there are daylife topics matching your query, you can use search_getMatchingTopics. This API returns you all the daylife topics which have a name containing all the words in your query.
Make sure you use a cannonical identifier for the topic. Try “Hillary Rodham Clinton”, or better yet, use topic_id “01EA6Cj8Fp6H7”.
The safest method for obtaining a topic is to do a search, e.g. search_getMatchingTopics(‘hillary clinton’), and it will return some topics, one of which will be “Hillary Rodham Clinton”, then pull the topic_id and use that in the topic_* calls.
When using the topic name, the topic_* calls are fairly strict – it has to be an exact match to the official topic name. if you use the topic_id instead of the name, then you also won’t have to worry if she changes her name back to “Hillary Rodham” – the topic_id will still be valid.
A list of sources can be downloaded here (last updated March 24, 2010).
An article is the atomic piece of content that gets published by a source. It has a headline, a publish date, an excerpt and an associated source that published it.
A story is a collection of related articles. The Daylife platform clusters articles about the same news event (in a 24 hour window) into a story to help the user easily navigate the news by looking at a smaller set of data i.e. the stories. On further interest about a particular story, a user can then dive into the articles that are contained in the story.
Every story has a representative article. The Daylife platform chooses this article in a cluster based on a range of factors to ensure that it is the best representative article for that news event.
You can get stories about a topic using the API topic_getRelatedStories. You can also get a stream of articles about a topic using the API topic_getRelatedArticles, however, you would then see more articles about the same news event in this case.
search_getMatchingTopics returns you topics (people, place or organization) whose name matches with the query term provided in the request. For e.g. if the request has "query=bush", the response will contain topics such as George W. Bush, Laura Bush or Jenna Bush. An empty list is returned if the provided query does not match the name of any topic, for example - "query=iraq war"
search_getRelatedTopics returns you topics that are mentioned in articles that contain the given query term. For e.g. - "query=bush" will return you topics that were mentioned in articles that mentioned "bush". Similarly, request with "query=iraq war" returns you topics that were mentioned in the articles that mentioned "iraq war"
Daylife tracks news from thousands of sources across the world. Sources include mainstream news such as the New York Times, blogs such as BuzzMachine, and other types of news content sources such as Getty Images for photos.
For your application, however, you may wish to restrict the results you retrieve to suppress certain sources, or to only feature content from specific sources.
Daylife API users can restrict the results of API calls to sources of their choice by creating and accessing source filters – i.e., whitelists or blacklists of news and image sources. When a source_filter_id (see below) is passed as a parameter to a Daylife API call, then the content returned is limited by those sources enumerated in the source filter's whitelist or blacklist.
Every source filter is identified by a source_filter_id. You can have as many source filters as you like, which you can use for various purposes. For example:
In the current version of the Daylife API, source filters are created and maintained by Daylife. Contact us at email@example.com if you'd like us to set up source filters for you.
You can decode php serialized response (of course in PHP) by using the unserialize function. You can read more about it here: http://php.net/unserialize.
Below is a list of functions/links that you can use in different languages to unserialize json serialized data: