http://diggapi.pbwiki.com/ RecentChanges for Digg API en http://diggapi.pbwiki.com/feedlogo.gif http://pbwiki.com/ PBwiki 3.7 support@pbwiki.com http://diggapi.pbwiki.com/ListStories email.hidden@example.com (KurtW) KurtW edited ListStories Note that the URL must be URL-encoded. For example:
http://services.digg.com/stories?link=http%3A%2F%2Fstamen.com%2Fclients%2Fcabspotting&appkey=http%3A%2F%2Fexample.com%2Fapplication
linkhash
MD5 hash of the URL of linked article.
String, e.g.: baab52e8474e83724d5a00de844fc133 is the MD5 hash of the URL: http://blog.digg.com/?p=130
For example: http://services.digg.com/stories?linkhash=baab52e8474e83724d5a00de844fc133&appkey=http%3A%2F%2Fexample.com%2Fapplication
media
Return stories of selected media.
]]> Mon, 21 Jul 2008 10:10:44 +0000 mod http://diggapi.pbwiki.com/BasicConcepts email.hidden@example.com (Steve Williams) Steve Williams edited BasicConcepts To use Digg's public API proxy, just change the URL of any API request to http://digg.com/tools/services. The proxy takes an "endPoint" query string argument specifying the Digg API endpoint requested, together with the other query string arguments from the API request.
Here's an example. The following direct API request asks for information about a page on the Digg Blog at http://blog.digg.com/?p=98:
http://services.digg.com/stories/?link=http%3A%2F%2Fblog.digg.com%2F%3Fp%3D98&appkey=http%3A%2F%2Fexample.com&type=xmlhttp://services.digg.com/stories?link=http%3A%2F%2Fblog.digg.com%2F%3Fp%3D98&appkey=http%3A%2F%2Fexample.com&type=xml
The corresponding call to the Digg's public API proxy is:
http://digg.com/tools/services?endPoint=/stories&link=http%3A%2F%2Fblog.digg.com%2F%3Fp%3D98&type=xml&appkey=http%3A%2F%2Fexample.com
]]> Thu, 10 Jul 2008 11:46:38 +0000 mod http://diggapi.pbwiki.com/ListContainers email.hidden@example.com (Steve Williams) Steve Williams edited ListContainers List Containers
from Digg. Digg. For each container, the short_name attribute may be used in a List Stories request, e.g. /stories/container/{container name}.
Example Request
Retrieve all Digg containers:
]]> Mon, 30 Jun 2008 13:47:00 +0000 mod http://diggapi.pbwiki.com/ListTopics email.hidden@example.com (Steve Williams) Steve Williams edited ListTopics List Topics
from Digg. Digg. For each topic, the short_name attribute may be used in a List Stories request, e.g. /stories/topic/{topic name}.
Example Request
Retrieve all Digg topics:
]]> Mon, 30 Jun 2008 13:45:22 +0000 mod http://diggapi.pbwiki.com/ListMedia email.hidden@example.com (Steve Williams) Steve Williams edited ListMedia List Media
on Digg. Digg. For each medium, the short_name attribute may be one of the values to the media argument of a List Stories request.
Example Request
Retrieve all Digg media
]]> Mon, 30 Jun 2008 13:43:55 +0000 mod http://diggapi.pbwiki.com/ListStories email.hidden@example.com (Steve Williams) Steve Williams edited ListStories 404 Not Found indicates that the given user does not exist.
GET /user/{user name}/dugg
given user. user, sorted most recent digg first.
404 Not Found indicates that the given user does not exist.
GET /user/{user name}/commented
given user. user, sorted most recent comment first.
404 Not Found indicates that the given user does not exist.
GET /user/{user name}/friends/submissions
404 Not Found indicates that the given user does not exist.
GET /user/{user name}/friends/dugg
user friends. friends, sorted most recent digg first.
404 Not Found indicates that the given user does not exist.
GET /user/{user name}/friends/commented
user friends. friends, sorted most recent digg first.
404 Not Found indicates that the given user does not exist.
Arguments
min_submit_date, max_submit_date
Get stories submitted within a given time period.
Not valid for these endpoints:
/]]> Mon, 19 May 2008 15:23:54 +0000 mod http://diggapi.pbwiki.com/ListContainers email.hidden@example.com (Steve Williams) Steve Williams edited ListContainers Example Request
Retrieve all Digg containers:
http://services.digg.com/media?appkey=http%3A%2F%2Fapidoc.digg.comhttp://services.digg.com/containers?appkey=http%3A%2F%2Fapidoc.digg.com
Example Responses
XML
]]> Tue, 13 May 2008 06:01:25 +0000 mod http://diggapi.pbwiki.com/ListMedia email.hidden@example.com (Steve Williams) Steve Williams edited ListMedia Example Request
Retrieve all Digg media
http://services.digg.com/containers?appkey=http%3A%2F%2Fapidoc.digg.comhttp://services.digg.com/media?appkey=http%3A%2F%2Fapidoc.digg.com
Example Responses
XML
]]> Tue, 13 May 2008 06:00:42 +0000 mod http://diggapi.pbwiki.com/FrontPage email.hidden@example.com (KurtW) KurtW edited FrontPage The Digg Application Programming Interface (API) has been created to let users and partners interact programmatically with Digg. The API returns Digg data in a form that can be easily integrated into an application or a web site. While the API is available to everyone free of charge, its use is subject to acceptance of our API License Agreement.
We intend to make most of the data on Digg.com available through the API. Currently, you can use the API to request very specific information about news stories and videos submitted to Digg, digging activity, comments, users, and gallery photos.
for PHP. PHP as well other open-source toolkits.
Thank you for interacting with and using the Digg API. If you have any questions, comments, or suggestions, please visit the DiggAPICommunitySupportForum.
Want to use the Digg API for commercial purposes? Contact us at partners@digg.com. Please provide as much detail as you can about your proposed application and how you would like the b]]> Wed, 23 Apr 2008 10:08:27 +0000 mod http://diggapi.pbwiki.com/FrontPage email.hidden@example.com (KurtW) KurtW edited FrontPage]]> Wed, 23 Apr 2008 10:04:25 +0000 mod http://diggapi.pbwiki.com/FrontPage email.hidden@example.com (KurtW) KurtW edited FrontPage Recent News
Digg's Public API Proxy and Good API Application Design
Apr 23th, 23rd, 2008
Latest API Updates
by Steve Williams at 4pm, Feb 4th, 2008
]]> Wed, 23 Apr 2008 10:03:56 +0000 mod http://diggapi.pbwiki.com/FrontPage email.hidden@example.com (KurtW) KurtW edited FrontPage Digg API
Recent News
Digg's Public API Proxy and Good API Application Design
by Kurt Wilms at 11am, Apr 23th, 2008
Latest API Updates
by Steve Williams at 4pm, Feb 4th, 2008
Gallery Photos
by Kurt Wilms at 6pm, Oct 25th, 2007
New API Features, Documentation for Community Review
by Kurt Wilms at 10pm, Sep 24th, 2007
Background
The Digg Application Programming Interface (API) has been created to let users and partners interact programmatically with Digg. The API returns Digg data in a form that can be easily integrated into an application or a web site. While the API is available to everyone free of charge, its use is subject to acceptance of our API License Agreement.
]]> Wed, 23 Apr 2008 10:03:38 +0000 mod http://diggapi.pbwiki.com/News email.hidden@example.com (KurtW) KurtW edited News News
Digg's Public API Proxy and Good API Application Design
by KurtWilms at 11am, April 23rd, 2008
We recently updated the API documentation with info about our public, cached API proxy. You'll find the new docs starting here: http://apidoc.digg.com/BasicConcepts#BePolitePlease
High-traffic applications, especially client-side applications like... widgets, toolbars, and Flash apps should cache API responses to avoid making lots of repetitive requests for the same data. The public API proxy is one convenient way to do that caching.
Enjoy,
Kurt
Latest API Updates
by SteveWilliams at 4pm, Feb 4th, 2008
]]> Wed, 23 Apr 2008 10:03:28 +0000 mod http://diggapi.pbwiki.com/BasicConcepts email.hidden@example.com (Steve Williams) Steve Williams edited BasicConcepts We monitor API usage, and we may block applications that do silly things. Use good judgment to keep your application running smoothly!
Caching API Responses
API responses, responses and so should use caching to avoid getting blocked. This is especially true if you have a high-traffic web site and you want to display Digg data directly on your web pages. All web sites, regardless of traffic, should use one of these methods to cache API responses:
Make the API request in your server-side code and cache the response.
Set up a cached proxy on your web site. If your web page calls the Digg API via AJAX, you'll need a proxy in any case, due to Javascript security, and it's straightforward to add a cache to your proxy. You're welcome to use Services_Digg_Proxy from PEAR Services_Digg to implement your proxy, and you can easily add caching.
]]> Tue, 22 Apr 2008 14:51:18 +0000 mod http://diggapi.pbwiki.com/BasicConcepts email.hidden@example.com (KurtW) KurtW edited BasicConcepts Note the timestamp in the response, and make another request with that timestamp as the min_date argument. The response will include items which immediately follow that timestamp, and a new value in the timestamp property.
Repeat step 2 to get even more current data.
remember, be polite: [#BePolitePlease|be polite]: Don't make requests every second, or our operations guys may see your application as an attacking robit. Consider making one request per minute, and processing or displaying the data between requests. That's how Stamen's flash toolkit does its magic.
Using Offsets
The offset and count arguments are used to ensure that each response is of a reasonable size. When a request specifies a large amount of data, such as many Diggs, users, or news items, each response provides only a portion of that data. Additional requests can retrieve, piece by piece, the desired result, by specifying an offset into the data and a count of elements to be returned. The maximum coun]]> Tue, 22 Apr 2008 14:41:26 +0000 mod http://diggapi.pbwiki.com/Toolkits email.hidden@example.com (KurtW) KurtW edited Toolkits Dustin has written a library in Java
Tim has written another library in Java
Headzoo wrote a JavaWrapper
Ruby
John has written a Digg API wrapper in Ruby
neaveru has written a JavaScript API Toolkit that can be used to create client side web pages that interact with Digg.
.NET
irhetoricHeadzoo has written a .NET wrapper.
]]> Thu, 10 Apr 2008 08:19:41 +0000 mod http://diggapi.pbwiki.com/LicenseAgreement email.hidden@example.com (Steve Williams) Steve Williams edited LicenseAgreement DIGG, INC. API LICENSE AGREEMENT
by Digg. Digg ("Digg Applications"). Licensee may not install or use the APIs for any other purpose (including without limit any commercial purpose) without Digg's prior written consent. For the sake of clarity, the sale of advertising on a website where a Digg Application is hosted shall not alone constitute a commercial use under this Agreement, provided that the advertising is not integrated within the Digg Application itself. Licensee shall not use the APIs in connection with or to ]]> Tue, 26 Feb 2008 09:58:24 +0000 mod http://diggapi.pbwiki.com/News email.hidden@example.com (Steve Williams) Steve Williams edited News Since Digg Images was released, we've also made some minor additions to the API responses:
ListStories now adds an inaccurate="1" attribute to each story that has been voted inaccurate by Digg users.
root attribute to each reply, to make it easier for applications to follow comment threads and link directly to individual comments. The level attribute gives the level of the comment within the thread, where the root of the thread is level zero. The root attribute gives the numeric ID of the root comment of the reply's thread.
ListUsers now adds an a fullname attribute to each user element, if the user has made it public.
The ListStories endpoints /users/{username}/friends/dugg and /users/{username}/friends/commented now return the friends who dugg or commented on each story.
user's
MicroID MicroID and profile links.
When we make changes like this, we always think about backward compatibility. In general, we believe that addi]]> Mon, 04 Feb 2008 16:24:10 +0000 mod http://diggapi.pbwiki.com/FrontPage email.hidden@example.com (KurtW) KurtW edited FrontPage Digg API
Recent News
Latest API Updates
by Steve Williams at 4pm, Feb 4th, 2008
Gallery Photos
by Kurt Wilms at 6pm, Oct 25th, 2007
New API Features, Documentation for Community Review
by Kurt Wilms at 10pm, Sep 24th, 2007
And the winner is…
by Daniel Burka at 7am, May 31st, 2007
Background
The Digg Application Programming Interface (API) has been created to let users and partners interact programmatically with Digg. The API returns Digg data in a form that can be easily integrated into an application or a web site. While the API is available to everyone free of charge, its use is subject to acceptance of our API License Agreement.
]]> Mon, 04 Feb 2008 16:09:47 +0000 mod http://diggapi.pbwiki.com/News email.hidden@example.com (KurtW) KurtW edited News News
Latest API Updates
by SteveWilliams at 4pm, Feb 4th, 2008
As you know, in December, we launched DiggImages and made some changes to how stories are organized on Digg. Naturally, at the same time, we enhanced the API so you can create applications that work more smoothly with the new Digg features. It was a challenge to ensure the enhancement didn't break existing applications.
When we added images to Digg's existing support for news and videos, we made a big related change: News, videos, and images all are organized under a single set of topics. (Before, videos topics were separate from news topics.)
We added two endpoints to allow applications to adapt seamlessly to changes like this in the future:
ListMedia returns the available media, currently news, videos, and images.
ListContainers returns the list of available topic containers, e.g. "Technology," "World & Business," and so on, and the topics within each container.
List Topics is still there, and]]> Mon, 04 Feb 2008 16:09:43 +0000 mod