Application Keys

The CGI argument appkey is required for all Digg API requests.

The value of the appkey argument is up to you, within the constraints described below. Digg does not issue or authenticate appkeys at this time. It is used only for statistical purposes.

You may not be able to keep your selected appkey secret. We can't think of any reason someone would want to sniff your appkey and use it for their own, but silly mischief is always a possibility.

The value of the appkey argument must be a valid absolute URI (see IETF RFC 2396) that identifies the application making the request. The URI might point to:

• The application itself, if it's a web application.
• A web page describing the application.
• A web page offering the application for download.
• The author's web site.

Or you may use a URI that doesn't actually point to a document on the worldwide web, but uniquely identifies your application.

The value of the appkey argument must be URL encoded (see IETF RFC 1738 Section 2.2).

In this example, the appkey is the URL-encoded form of:

http://www.example.com/application

Example:

http://services.digg.com/user/sbwms?appkey=http%3A%2F%2Fwww.example.com%2Fapplication

Note that example.com is not a valid appkey! It's only an example. Requests with example.com in the appkey will not receive a response. You must choose your own appkey appropriate to your application.