Upgrading To v4 IGDB API From v3 IGDB API

May 2022: Another way of doing this is using the AWS Proxy Functionality, which does automatic token rotation. https://api-docs.igdb.com/#proxy

https://api-docs.igdb.com/#upgrading-to-v4-from-v3

https://medium.com/igdb/igdb-api-v4-is-coming-6ba97874edbc

  • Update Endpoints
  • Change GET requests to POST
  • Verify WebHooks
  • Update Authentication to Twitch (Need to generate a Token using Client-ID + Client Secret somehow....)

Find a method to create / generate & validate the API Keys automatically https://dev.twitch.tv/docs/authentication/#validating-requests

  • Investigate a method to store API Details Automatically (And securely) by default in the PHP
  • Investigate if it's possible to sign in "Just using twitch" from a user perspective (So they don't need dev accounts)

@edstub207 No, the auth tokens are only valid for 60 days and then you need to fetch new ones As for the frontend plugin solution. Codecrsher wrote "we expect api users to have a backend system that calls out service. You can build mobile or desktop apps, but they should not connect directly to our API. We wanted a clear and simple path for migrating to v4, and app tokens are the way to do that. Client tokens require an oauth flow and signing in with Twitch. This is a non-starter for apps that already have their own login flows." A few days ago

  • Verify and Remove/Update Endpoints with V4 Changes
  • Verify and Remove/Update Fields with V4 Changes

Popularity was removed because it doesn't work properly https://twitch.uservoice.com/forums/929953-igdb/suggestions/40888234-popularity-attribute-not-functional

  • Update README with above changes + findings + actions
  • Update guide on how to use plugin + screenshots if needed
  • Run security checks with new changes
  • Perform any backend upgrades required
  • Investigate IGDB Proxy Service https://api-docs.igdb.com/#proxy
  • Look into "Follows" as a filter option instead image
Edited by Eddie Stubbington