boggydigital: Hey folks, fantastic information so far in this thread! I'm working on a Golang (self-hosted) local GOG website called vangogh (I have some things implemented here:
https://github.com/arelate) and stumbled upon the following problem:
I'm trying to get a consistent source of the data for indexing (search, view models), something along the lines of id, title, publisher, developer(s), rating, languages, etc.
api.gog.com/v2/games/{id} seems like a great source for games - store products and account products seem universally available (with exceptions like "Spring Sale Goodies Collection #1":
https://api.gog.com/v2/games/2005648906), however I couldn't find how to make that work for movies. Neither /games/{movie_id}, nor /movies/{movie_id}, nor /{movie_id} works.
api.gog.com/products/{id} does seem to work for games AND movies, however it doesn't seem to contain things like publisher, developer, rating even with available `expand` values (perhaps I'm missing some?).
My current backup plan is to use response from /games/ajax/filtered?mediaType=movies and hope that it'll correspond with account products, unlike games (regional versions, bundles) - less than ideal since that'll be a separate code-path for movies.
Any ideas on data sources that would ideally allow to do this consistently between games and movies would be appreciated!
Abstract and cache if possible. This is my first time seeing this stuff (from first post to jumping to last page, so keep that context in mind), but ask yourself how you'd implement it. Would you use the same database for both games and movies? Given it's made for Galaxy, i expect it to have whatever is available for Galaxy. Therefore, if Galaxy has it, there's a safe way to grab it. If Galaxy doesn't display it, i would assume it's apocrypha not gospel. I don't use galaxy, so i wouldn't know.