/sourceforge/projects/downloads

POST /api/sourceforge/projects/downloads

Price: 5 credits

Get SourceForge project download statistics over a date range

How to use it

Get download statistics for a SourceForge project over a date range (defaults to the last 30 days). Returns total downloads, the daily download series, per-country and per-operating-system breakdowns, and the top country/OS with their share.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• project string required — Project shortname/slug or a SourceForge project URL (examples: "sevenzip", "https://sourceforge.net/projects/sevenzip/"; minLength: 1)
• start_date string nullable — Range start date in YYYY-MM-DD format. Defaults to 30 days before end date. (examples: "2025-01-01")
• end_date string nullable — Range end date in YYYY-MM-DD format. Defaults to today. (examples: "2025-01-31")

Response

• @type string (default: "SourceforgeDownloadStats")
• total integer (default: 0)
• period string (default: "")
• start_date string (default: "")
• end_date string (default: "")
• stats_updated_at integer nullable
• last_period_incomplete boolean (default: false)
• top_country string nullable
• top_country_percent number nullable
• top_os string nullable
• top_os_percent number nullable
• daily array (default: [])
  • @type string (default: "SourceforgeDailyDownload")
  • date string (default: "")
  • count integer (default: 0)
• countries array (default: [])
  • @type string (default: "SourceforgeCountryDownload")
  • country string (default: "")
  • count integer (default: 0)
• operating_systems array (default: [])
  • @type string (default: "SourceforgeOSDownload")
  • os string (default: "")
  • count integer (default: 0)

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Project not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.