Repository navigation
[Feature Request]: Public API #253
Description
Description
I'm looking for a public API that can handle searching the database for games by name and/or IGDB or other metadata provider ID.
Would also be great if certain data could be pulled from the database in a programmatic way to provide performance tags and other relevant emulator data.
Additional context
I run the Hasheous project (https://hasheous.org/) which is used by the Romm and Gaseous ROM managers, and would like to be able to provide these projects with links to data held by Emuready.
At a minimum I would like to be able to provide to Hasheous consumers links to Emuready game pages. However, Hasheous also supports proxying data sources (currently IGDB, TGDB, and hopefully eventually GiantBomb), so I would also love to be able to proxy Emuready data (either by scheduled dump and load, or by caching API calls).
Checklist
- I have checked that this feature request has not already been suggested
- I have provided sufficient context and motivation
- I am willing to help implement this feature if needed
Activity
Producdevity commentedon Dec 16, 2025
Sounds interesting! Reach out on discord please :)
ApatheticRiku commentedon Oct 22, 2026
@michael-j-green or @Producdevity -- Is there any update on this request? I came here because I think an integration like this into RomM would be great, and was willing to work on it.. But if it can be proxied through Hasheous, that would be great too!
michael-j-green commentedon Oct 22, 2026
I totally forgot about this! Had some personal things happen and lost track. Apologies to all involved.
I'll reach out to @Producdevity
Producdevity commentedon Oct 22, 2026
@ApatheticRiku @michael-j-green my apologies to both of you! I have been kinda overwhelmed with maintaining this project by myself and at some point many issues turned out to be low effort spam tickets. I am afraid this one got buried and completely forgot about it.
I do think this needs some alignment first before a contribution can be made to not put too much stress on the server. If all data is relevant we could ideally have a scheduled large db dump or heavily cached endpoint specific for these types of usecases. Definitely reach out on discord, I haven't looked at my message requests for a while but promise to do so this weekend