Implementation Guide - Games

LEGACY Documentation for deprecated API version. For current documentation and up-to-date technical info, please visit here.
Recommended Implementation

When implementing games using the API IVA recommends the following approach:

  1. Use /Games/All endpoint to get and cache all the game objects. Be sure to include any additonal objects as needed.
  2. Use the /Changes/Games/History endpoint to get Movie IDs of any movie object that has changes.
  3. Use the /Games/{Id} endpoint to get the updated movie object and replace what is stored in cache.
Get All Games

Start with GetAllGames(/Games/All) paging through all the results. Include any additional objects (Videos, Descriptions, etc.) to be returned. Store each game object in a database for easy updating.


Usage and SDK Samples

curl -X get -H "Ocp-Apim-Subscription-Key: [[apiKey]]" ""
Get Updated Game Id's

Use the Changes APIs, GetGameChangeHistory(/Changes/Games/History) to keep the data up-to-date. IVA recommends updating once a day to get any updates.


Usage and SDK Samples

curl -X get -H "Ocp-Apim-Subscription-Key: [[apiKey]]" ""

Update Game

For each GameId that has been updated, update the data in your database by calling GetGame(/Games/{Id}) and replacing the full object. Developers are encouraged to check for updates often to keep the data fresh and to be aware of new video assets and images added to the library.


Usage and SDK Samples

curl -X get -H "Ocp-Apim-Subscription-Key: [[apiKey]]" "{Id}?includes="