> For the complete documentation index, see [llms.txt](/llms.txt)

# GS2-Version API Reference

Version check feature




Provides game version checks.
After a version check succeeds, a new project token can be issued.
This allows credentials embedded in the game to have only enough permission to log in and perform the version check, while the token issued after a successful check has the permissions needed to play the game.

A namespace can define up to ten version models, and the check succeeds only when every model satisfies its requirement.
Two model types are available: passive checks based on versions sent by the application, and active checks based on versions previously accepted by the logged-in user.

- Passive checks are used for application binaries and downloaded assets and can return warning or error results according to configured thresholds.
- Active checks are used for EULAs and privacy policies, with the accepted version stored on the server so that agreement cannot be bypassed by changing a client value.

[Introduction to Microservices / GS2-Version](../../microservices/version)



- [GS2-Version Deploy/CDK Reference](/api_reference/version/deploy/)
  
- [GS2-Version Master Data Reference](/api_reference/version/master_data/)
  
- [GS2-Version Script Trigger Reference](/api_reference/version/script/)
  
- [GS2-Version SDK API Reference](/api_reference/version/sdk/)
  
- [GS2-Version SDK for Game Engine API Reference](/api_reference/version/game_engine/)