Giant Bomb API Error

[mattsigal]

• The Plugin is up to date - running the latest pre-release version via Brat
• Obsidian is up to date (v 1.10.6)

Describe the bug
Accessing the Giant Bomb API to add a videogame now gives a 404 error.

Error: MDB | Received status code 404 from GiantBombAPI.
    at $i.searchByTitle (plugin:obsidian-media-db-plugin:38:16868)
    at async eval (plugin:obsidian-media-db-plugin:35:1295)
    at async Promise.all (index 2)
    at async Ei.query (plugin:obsidian-media-db-plugin:35:1416)
    at async eval (plugin:obsidian-media-db-plugin:90:3990)
    at async jn.openSearchModal (plugin:obsidian-media-db-plugin:88:1491)
    at async Wn.createEntryWithSearchModal (plugin:obsidian-media-db-plugin:90:3810)
eval @ plugin:obsidian-media-db-plugin:35
18:46:04.133 plugin:notice-logger:82 [2025-12-09 18:46:04] Error querying GiantBombAPI: Error: MDB | Received status code 404 from GiantBombAPI.

To Reproduce
Steps to reproduce the behavior:

1. Open the Add Videogame modal
2. Search for a game
3. See the error message

Expected behavior
Should successfully query the API for the title, as it did before.

Occurs on

• [X ] Windows

Plugin version
0.8.0-canary-20251127T201949

Additional context
I believe Giant Bomb was recently sold and is under new ownership. However, in my Profile page, I still have an API key listed so I believe the API is still live but maybe the access structure has changed?

[mattsigal]

Edit: I looked into this some more and it turns out the new owners have taken down the API access. I guess it is time to remove Giant Bomb from the plug-in options.

It would be fantastic to replace it with a different option. I believe the following might be good choices:

1. IGDB (Internet Game Database)
2. RAWG.io

As far as I can tell, IGDB is the industry standard (owned by Twitch) and free, while RAWG offers a simpler API key setup that might be easier for users to configure.

[ltctceplrm]

The Giantbomb wiki is switching to mediawiki and the work is still ongoing so the api has not yet been re-enabled but normally it should come back eventually.

I'm not sure how long this might take but I suggest just waiting for now.

[Lorite]

Hi @ltctceplrm . Do you know how long should we wait? Are we sure the issue will fix itself and that we don't need to implement a new API service?

[ltctceplrm]

There is some ongoing discussion for how exactly the API would be brought back and there is no definite timeline for when or even assurance that it will return, it's not a priority for giantbomb compared to working on the wiki itself.

So if you want to add support for another API it's definitely not a bad idea.

[Lorite]

I have vibe coded a quick solution and it works. I can't create a PR now because I have some other changes in my fork and I don't have the time. Sorry. But feel free to get some inspiration! I would have also liked to implement it using a json scheme, but I don't know how. Lorite@6a91c44