Errors

HTTP Status Codes
Gameball uses HTTP response status codes to indicate the success or failure of your API requests. If your request fails, Gameball returns an error using the appropriate status code.
2XX codes indicate success and that the request worked as intended
4XX codes indicate errors due to some mistakes in the request.
5XX codes indicate an error with Gameball's servers.
Error Object
When an error occurs and the response code is 4XX, Gameball's servers send an Error Object that has two parameters, codeand message.
Example
{
    "code": 15,
    "message": "Name Already Exists"
}
Error Codes
Gameball sends an error code in the body of the response, each code has a corresponding error message that is descriptive of what went wrong, below are the codes along with their description.
Code
Message
Description
4
Missing Arguments
Missing parameter in the argument
​
Username is required for manual rewarding
​
Reason is required for manual rewarding
5
Null Arguments
The format is invalid or not compatible
7
Invalid Value
Value is in the wrong format, for example negative value for a payment
​
No level order was found matching the provided value
11
Hash Invalid
Hashed calculated is invalid or created in a wrong way
16
Inactive
Inactive element like a player or program that are inactive
17
Invalid Leveling Method
Different leveling method required to perform level update
101
Player External ID Not Found
Player does not exist
151
Referral Player Referred Already 
Customer already exists and can not be referred
152
Referral Code Not Found
Referral code is wrong or nonexistent
301
Transaction Type Non Reversible
This transaction can not be canceled or reversed
302
Transaction Already Canceled
The transaction has already been canceled
303
Transaction Not Found
Transaction ID doesn't exist
304
Transaction Time Already Exists
A transaction was already done during the same exact time
305
Transaction ID Already Exists
Transaction ID must be unique, this ID already exists
306
Transaction Reversed ID Not Found
Reversed Transaction ID doesn't exist
307
Transaction Hold Reference Not Found
Transaction Hold Reference no longer exists. It is either wrong or it's been deleted after the 10-minute hold
351
Event Not Found
This event is not configured in the dashboard
The table covers all used errors and their description. If you get any error that is not listed above, please email us to add it.

Notifications Webhook

Next - REST API

Object Reference

Last modified 1yr ago

Copy link

Outline