Legacy endpoints returning 0 for “giantbomb_id” following IGDB migration

Following Twitch’s migration to IGDB for game information, we unfortunately missed one update that would affect third-party developers. Legacy endpoints that included a giantbomb_id field now return a value of 0 as a result and we regret not catching this before the migration to properly inform developers.

Who will be impacted by these changes?

Any developer who has been using one of the following endpoints should expect a value of 0 for the giantbomb_id field.

Why are we making these changes?

With the migration to IGDB, we no longer track Giant Bomb game information. We have received feedback to add IGDB game IDs to relevant Twitch API endpoints, and while this is not currently available, we recommend you follow or upvote the following UserVoice idea to track this potential addition.

As noted on the linked uservoice for those not clicking it :stuck_out_tongue: .

You can use your existing app access token against the IGDB Api and lookup from IGDB with the Twitch’s ID instead

HTTP POST -> https://api.igdb.com/v4/games/

With body:

fields *; where external_games.category = 14 & external_games.uid = "TWITCHGAMEID";
1 Like