Summary
SourceForge exposes an unmaintained, read-only "API" for public project data. Standard XML data formats like DOAP and RSS are used extensively. You can semantically "discover" many of the RSS endpoints from a project's DOAP endpoint.
Conventions
- Access all endpoints via HTTP GET
- Access all endpoints via the following URI scheme: /api/{resource}[/index][/{parameter}/{value}]...[/{format}]
- Request alternative representation formats with a trailing format identifier on the URI. e.g.,
- Traverse RSS feeds by "paging" with the following conventions:
- Supply a /limit/N url parameter (a maximum limit of 100 is always imposed). e.g.,
- Supply a /offset/N url parameter. e.g.,
- Follow the //rss/channel/sf:next "link" found on every RSS. e.g.,
- <sf:next>/api/artifact/index/tracker-id/612382/limit/30/offset/60/rss</sf:next>
Resources
Project
Parameters
Index:
- changed_since
- new_since
Other:
- name
- id
Formats
- doap
- json
Examples
- http://sourceforge.net/api/project/index/new_since/1272409091/rss
- http://sourceforge.net/api/project/name/tangoiconsprite/doap
- http://sourceforge.net/api/project/id/156708/json
User
Parameters
- username
- id
Formats
- json
- rss
Examples
- http://sourceforge.net/api/user/username/lukecrouch/json
- http://sourceforge.net/api/user/id/1414701/rss
File Releases
Parameters
- project-id
- package-id
- path
- recursive
- order_by
Formats
- rss
Examples
Project News
Parameters
- project-id
- since
Formats
- rss
Examples
Forum Posts
Parameters
- forum-id
Formats
- rss
Examples
Tracker Artifacts
Parameters
- tracker-id
- since
Formats
- rss
Examples
Mailing List Messages
Parameters
- list-name
Formats
- rss
Examples
Activity
Parameters
- project-id
- since
Formats
- rss
