decomp.me APIdecomp.me ↗
Access decomp.me decompilation projects, user contributions, and site statistics via 4 endpoints. Retrieve scratch details, source code, compiler flags, and scores.
curl -X GET 'https://api.parse.bot/scraper/28e2a231-d752-4389-890d-c31ca235a587/get_recent_scratches?page_size=5' \ -H 'X-API-Key: $PARSE_API_KEY'
Retrieve the latest decompilation projects and site activity. Returns a paginated list of scratch projects sorted by the specified ordering.
| Param | Type | Description |
|---|---|---|
| ordering | string | Sort order for results. Accepted values: '-creation_time' (newest first), '-last_updated' (recently edited first). |
| has_owner | string | Filter for scratches with a registered owner. Accepted values: 'true', 'false'. |
| page_size | string | Number of results per page. |
{
"type": "object",
"fields": {
"next": "string or null, URL for next page of results",
"results": "array of scratch summary objects containing slug, owner, name, platform, compiler, score, max_score, creation_time, last_updated",
"previous": "string or null, URL for previous page of results"
},
"sample": {
"data": {
"next": "https://decomp.me/api/scratch?cursor=cD0yMDI2LTA1LTA3&has_owner=true&ordering=-creation_time&page_size=5",
"results": [
{
"name": "func_80069220",
"slug": "lOeY3",
"owner": {
"id": 8779709,
"username": "Shy Wolverine (anon)",
"is_anonymous": true
},
"score": 37625,
"parent": null,
"preset": 136,
"compiler": "ido5.3",
"platform": "n64",
"libraries": [],
"max_score": 41800,
"last_updated": "2026-05-07T15:12:13.692098+09:00",
"creation_time": "2026-05-07T15:07:07.430953+09:00",
"match_override": false
}
],
"previous": null
},
"status": "success"
}
}About the decomp.me API
The decomp.me API exposes 4 endpoints for querying decompilation scratch projects, user contributions, and site-wide statistics on decomp.me. The get_scratch_detail endpoint returns full project data including C source code, compiler flags, target platform, match score, and version family history — giving programmatic access to the same data visible on individual scratch pages.
Endpoints and Data Coverage
The API covers four areas of decomp.me. get_recent_scratches returns a paginated list of scratch projects sortable by -creation_time or -last_updated, with optional filtering by whether a scratch has a registered owner via the has_owner parameter. Each result includes the scratch slug, owner, name, platform, compiler, score, max_score, creation_time, and last_updated. The page_size parameter controls how many results appear per page.
Scratch Detail
get_scratch_detail accepts a slug (obtainable from get_recent_scratches results) and returns the complete record for that project: the source_code string containing the C decompilation attempt, the context header used for compilation, the compiler identifier, the platform tag (e.g. n64, gc_wii), and a family array listing related scratch version summaries. The score and max_score integers together indicate how closely the compiled output matches the target assembly.
User Contributions and Site Stats
get_user_contributions takes a GitHub/decomp.me username and returns that user's scratch projects in the same paginated format as get_recent_scratches, with the same ordering and page_size controls. get_stats requires no parameters and returns three site-wide counters: asm_count (total assembly instructions across all scratches), scratch_count (total projects), and github_user_count (registered users). These are useful for tracking platform growth over time.
- Monitor newly created or recently updated decompilation scratches using
get_recent_scratcheswith-last_updatedordering. - Build a leaderboard by collecting
scoreandmax_scorefields from multiple scratches to rank contributors by match quality. - Audit a specific contributor's output by fetching all their scratches via
get_user_contributionswith their GitHub username. - Diff decompilation approaches across related scratch versions using the
familyarray returned byget_scratch_detail. - Track platform-specific activity by filtering
get_recent_scratchesresults by theplatformfield (e.g.n64,gc_wii). - Aggregate site growth metrics over time by polling
get_statsfor changes inscratch_countandgithub_user_count. - Extract C source code and compiler context from a scratch using
source_codeandcontextfields for offline analysis.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does decomp.me have an official developer API?+
What does `get_scratch_detail` return beyond what the list endpoints show?+
get_scratch_detail adds four fields not present in list results: source_code (the full C decompilation text), context (the C header context passed to the compiler), the family array of related scratch version summaries, and the compiler string. The list endpoints only carry summary fields like slug, name, score, max_score, platform, and timestamps.Can I filter scratches by platform or compiler?+
get_recent_scratches supports filtering by has_owner and sorting by ordering, but platform and compiler filtering is not exposed as a parameter. You can retrieve paginated results and filter on platform or compiler client-side using the fields present in each result object. You can also fork this API on Parse and revise it to add a platform or compiler filter endpoint.Is assembly output or diff data available from the API?+
source_code (C source), context, score, and max_score, but does not expose the compiled assembly output or the line-by-line diff between the attempt and the target. You can fork this API on Parse and revise it to add an endpoint that surfaces assembly diff data if decomp.me exposes it via their public API.How fresh is the data returned by these endpoints?+
get_recent_scratches sorted by -last_updated returns projects in the order they were most recently edited, so the freshness of any given scratch depends on when its author last saved changes. There is no delta or webhook mechanism — callers need to poll periodically to detect updates.