Apidoc Glossary

Name	Description
FUNGAMESS	Component used as mediator between Product provider and ThirdPartyPlatform FUNGAMESS ensures seamless integration of Products to ThirdPartyPlatforms All requests, originated from Product provider, are aggregated and presented to ThirdPartyPlatform in a unified way Thus, ThirdPartyPlatform doesn't have any ability to handle any specific Products
ThirdPartyPlatform	Party that integrate Products via FUNGAMESS mediation ThirdPartyPlatform is an owner of User accounts, and handles User balances In the Workflow diagram and Sportbook integration is displayed as Client
Token	Authentication token for logged player (provided by the ThirdPartyPlatform)
Casino API methods	List of methods for operating the Casino
Outbound Call API	HTTP requests FROM ThirdPartyPlatform TO FUNGAMESS
Callback API	HTTP requests FROM FUNGAMESS TO ThirdPartyPlatform
Notifications	HTTP requests from FUNGAMESS to Third PartyPlatform This section contains a list of requests required to notify the ThirdPartyPlatform These requests notify about possible limits reach, maintenance or game restrictions
Sport API methods	List of methods for operating with Sport
base_url	The link that is used by ThirdPartyPlatform to reach the FUNGAMESS for the required information This method is added after base_url, to ensure the functionality of certain methods
callback_url	The link that FUNGAMESS uses to contact ThirdPartyPlatform to get the required information This method is added after callback_url, to ensure the functionality of certain methods
Key	The key that is used in the Hash-Authorization for Callback API request
Back office	Admin panel for the platform's setup and interaction
Hash-Authorization	Obligatory field in the Callback API request header to confirm that the call was received from the FUNGAMESS system This key is generated automatically, and is based on the following formula: sha256(['REQUEST_GET']['KEY']) You can see your KEY, received from "Integration → Config" settings page, at your back office on FUNGAMESS
Player	A person who performs activity on the client's platform For example: registering, playing games, betting, etc
Event	A specific action or outcome that occurs within a gaming session that triggers a financial transaction, such as placing a bet, winning, losing etc Events take place on the platform side A list of event types can be viewed here
Round	A single gameplay cycle, from placing a bet to receiving the result The round takes place on the aggregation side