Skip to main content

Apidoc Glossary

NameDescription
FUNGAMESSA component used as a mediator between the Product Provider and the ThirdPartyPlatform
FUNGAMESS ensures seamless integration of Products into ThirdPartyPlatforms
All requests originating from the Product Provider are aggregated and presented to the ThirdPartyPlatform in a unified format
Thus, the ThirdPartyPlatform does not need to handle any specific Products directly
ThirdPartyPlatformA party that integrates Products via FUNGAMESS mediation
The ThirdPartyPlatform owns user accounts and manages user balances
In the Workflow diagram and Sportbook integration, it is referred to as the Client
TokenAn authentication token for a logged-in player (provided by the ThirdPartyPlatform)
Casino API methodsA list of methods used to operate casino features
Outbound Call APIHTTP requests sent from the ThirdPartyPlatform to FUNGAMESS
Callback APIHTTP requests sent from FUNGAMESS to the ThirdPartyPlatform
NotificationsHTTP requests sent from FUNGAMESS to the ThirdPartyPlatform
This section contains a list of requests used to notify the ThirdPartyPlatform about possible limits being reached, maintenance activities, or game restrictions
Sport API methodsA list of methods used to operate sport-related features
base_urlThe endpoint used by the ThirdPartyPlatform to request data from FUNGAMESS
This method is added after base_url to ensure the functionality of certain methods
callback_urlThe endpoint FUNGAMESS uses to request data from the ThirdPartyPlatform
Methods are appended to the callback_url to enable specific functionality
KeyA key used in Hash-Authorization for Callback API requests
Back officeThe admin panel used for platform setup and interaction
Hash-AuthorizationA required field in the Callback API request header, used to confirm the request was made by the FUNGAMESS system
This key is generated automatically using the following formula:
  • sha256(['REQUEST_GET']['KEY'])
  • You can view your KEY on the "Integration → Config" settings page in your FUNGAMESS back office
    PlayerA person who performs actions on the client’s platform, such as registering, playing games, or placing bets
    EventA specific action or outcome within a gaming session that triggers a financial transaction, such as placing a bet, winning, or losing
    Events occur on the platform side
    A list of event types can be found here
    RoundA single gameplay cycle, from placing a bet to receiving the result
    The round is processed on the aggregation side