/sourceforge/projects/search

POST /api/sourceforge/projects/search

Price: 5 credits

Search the SourceForge project directory by keyword with category and OS filters

How to use it

Search the SourceForge open-source project directory by keyword, optionally filtered by category and operating system; or browse without a keyword by category, OS, programming language, development status, or natural-language translation, with an optional sort order. Development-status and translation browsing must be used on their own. Returns each project's slug, name, tagline, description, icon, star rating, review count, weekly downloads, and last-update time.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string nullable — Free-text search keyword (examples: "video editor", "qbittorrent")
• count integer required — Number of projects to return (min: 1; max: 25)
• category string nullable — Filter by top-level project category/topic (one of: "artificial-intelligence", "blockchain", "business", "communications", "database", "desktop-environment", "education", "formats-and-protocols", "games", "internet", "mobile", "multimedia", "printing", "productivity", "religion-and-philosophy", "scientific-engineering", "security", "social-sciences", "software-development", "system", "terminals", "text-editors")
• os string nullable — Filter by supported operating system (one of: "windows", "mac", "linux", "bsd", "chromeos", "mobile-operating-systems", "desktop-operating-systems", "server-operating-systems", "embedded-operating-systems", "game-consoles")
• programming_language string nullable — Browse by programming language. Only available without a keyword query. (one of: "actionscript", "ada", "algol-68", "apl", "applescript", "asp", "asp.net", "aspectj", "assembly", "autoit", "awk", "basic", "blitzmax", "boo", "c", "c-plus-plus", "c-sharp", "clarion", "cobol", "coffeescript", "cold-fusion", "common-lisp", "crystal", "curl", "d", "dart", "delphi-kylix", "eiffel", "elixir", "emacs-lisp", "erlang", "euler", "euphoria", "f-sharp", "filemaker-script", "flex", "forth", "fortran", "free-pascal", "gambas", "glsl-opengl-shading-language", "go", "groovy", "haskell", "haxe", "idl", "java", "javascript", "jsp", "julia", "kaya", "kotlin", "labview", "lazarus", "lisp", "logo", "lotusscript", "lpc", "lua", "mathematica", "matlab", "modula", "mumps", "oberon", "object-pascal", "objective-c", "objective-c-2.0", "ocaml-objective-caml", "opencl", "oz", "pascal", "perl", "php", "pike", "pl-i-programming-language-one", "pl-sql", "powershell", "progress", "prolog", "python", "r", "realbasic", "rebol", "rexx", "ruby", "rust", "s-r", "scala", "scheme", "scilab", "scriptol", "simulink", "smalltalk", "solidity", "standard-ml", "swift", "tcl", "transcript-revolution", "typescript", "unix-shell", "vala", "vbscript", "vhdl-verilog", "visual-basic", "visual-basic-.net", "visual-basic-for-applications-vba", "visual-foxpro", "xbase-clipper", "xbasic", "xsl-xslt-xpath-xsl-fo", "yacc", "zope")
• status string nullable — Browse by development status. Only available on its own, without a keyword or other filter. (one of: "planning", "pre-alpha", "alpha", "beta", "production-stable", "mature", "inactive")
• translation string nullable — Browse by natural-language translation. Only available on its own, without a keyword or other filter. (one of: "abkhazian", "afar", "afrikaans", "akan", "albanian", "amharic", "arabic", "aragonese", "armenian", "assamese", "aymara", "azerbaijani", "bambara", "basque-euskara", "belarusian", "bengali", "bosnian", "brazilian-portuguese", "breton", "bulgarian", "catalan", "central-khmer", "chechen", "chinese-simplified", "chinese-traditional", "croatian", "czech", "danish", "dutch", "english", "esperanto", "estonian", "faroese", "finnish", "french", "galician", "georgian", "german", "greek", "gujarati", "haitian", "hausa", "hebrew", "hindi", "hungarian", "icelandic", "igbo", "indonesian", "inuktitut", "irish-gaelic", "italian", "japanese", "javanese", "kannada", "kashmiri", "kazakh", "kinyarwanda", "kirghiz", "korean", "kurdish", "latin", "latvian", "lithuanian", "luxembourgish", "macedonian", "malagasy", "malay", "malayalam", "maltese", "marathi", "mongolian", "navajo", "nepali", "north-ndebele", "norwegian", "norwegian-bokmal", "norwegian-nynorsk", "occitan", "oriya", "oromo", "panjabi", "persian", "polish", "portuguese", "quechua", "romanian", "romansh", "rundi", "russian", "sanskrit", "scottish-gaelic", "serbian", "sindhi", "sinhala", "slovak", "slovene", "somali", "spanish", "sundanese", "swahili", "swedish", "tagalog", "tajik", "tamil", "tatar", "telugu", "thai", "tibetan", "tigrinya", "tswana", "turkish", "turkmen", "twi", "uighur", "ukrainian", "urdu", "uzbek", "venda", "vietnamese", "walloon", "welsh", "western-frisian", "wolof", "xhosa", "yoruba", "zulu")
• sort string nullable — Result ordering when browsing by category, operating system, or programming language (not available with a keyword query or with status/translation browsing). (one of: "popular", "update", "name", "rating")

Response

• @type string (default: "SourceforgeSearchProject")
• alias string required
• name string (default: "")
• tagline string nullable
• description string nullable
• image string nullable
• rating number nullable
• review_count integer nullable
• weekly_download_count integer nullable
• updated_at integer nullable
• web_url string (default: "")

Errors

• 422 — Invalid filter combination 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 — The entity was not found, or a precondition failed 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.