Response Codes | Staging Site

Conventional HTTP response codes are used to indicate the success or failure of an API request. In general:

2xx responses usually indicate success.
4xx responses usually indicate an error that failed given the information provided (e.g., a required parameter was omitted etc.).
5xx responses usually indicate an error with MG+ servers.

This table houses a list of possible response codes, a general explanation about the response and the possible solutions you could take to resolve the error.

Please note that these response codes are only applicable to the MG+ Single Wallet API, and not the MG+ Single Wallet Agent API. The MG+ Single Wallet Agent API has its own response codes.

Response Code	Meaning	Possible Solutions
200	A general code indicating a successful request and response.
201	A code indicating that the request to the system was performed successfully.
400	Input validation unsuccessful. Typically triggered by incorrect data input within the parameters.	Ensure the syntactic accuracy of the request body, path parameters, and query parameters.
401	A code denoting that the request was unauthorized due to the absence of a valid token provided.	Verify that you’ve transmitted an authorized API token within the Authorization header. In the event of token expiration, generate a fresh token.
403	A code denoting that the request was forbidden, as the API key does not have permission to perform the request.	Obtain the required scopes essential for performing the request. Contact support to ensure that your IP is whitelisted to call the API.
404	The requested resource (such as a game, player, or an agent code) does not exist.	Make sure that the resource you want to access exists.
409	The request could not be processed because of a conflict in the request.	Analyze the message returned by the API response to resolve the issue.
429	Too many requests sent in a short amount of time.	Reduce the number of requests Try again later
500	Internal server error.	An internal server error has occurred. Please try again later. Should the problem persist, please contact support.