Authentication

The Gameball API uses API keys to authenticate requests. You can view your API keys in the Gameball Dashboard.

Gameball APIs are authenticated using API Keys. API Keys add an additional layer of security to your account. The provided API Keys are namely, API Key and Secret Key (also defined as transaction key).

The API Key can be used for regular non-sensitive endpoints, for instance, create player, while the Secret Key is used along with the API Key when performing sensitive operations. Sensitive API endpoints that require Secret (transaction) key are:

Highly Important Note! Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret (transaction) key in publicly accessible areas such as GitHub, client-side code, and so forth.

Accordingly, you need to provide your account's API Key and (in some cases) Secret Key as well in the header with every request. Check this article on our Help Center for more information on how to get your API Key and Secret Key.

Note! API requests executed without authentication will fail.

Below is an example of the authentication through API Key header.

curl --request POST \
--url 'https://api.gameball.co/api/v3.0/integrations/event' \
--header 'APIKey: ue7eh32eiwlsncoko08u8b'

Also, below is an example of the authentication using both API Key and Secret Key.

curl --request POST \
--url 'https://api.gameball.co/api/v3.0/integrations/transaction/cashback' \
--header 'APIKey: ue7eh32eiwlsncoko08u8b'
--header 'SecretKey: kz7eh32eiwldlowbo08u5p'