Error Codes
Learn more about error codes
Some responses from the LootLocker API will include an error code. These error codes are designed to help you understand what went wrong with your request. Errors containing codes will always follow a common schema:
request_id
andtrace_id
are unique identifiers for the request and trace, respectively. These are important pieces of information to provide when contacting support for troubleshooting, as they allow the support team to quickly locate the details of the specific transaction in question.code
indicates the type of error. This is the field you should use to determine how to handle the error in your code. The possible values are documented below.doc_url
provides a link to the documentation for further information about this error code.message
provides a brief, human-readable description of the error. It's important to note that this field should not be used for flow control in your code, as its content may change and is not guaranteed to be consistent. It is intended for debugging and logging purposes, and to provide a readable error message to the end user.
Some error codes may also include additional fields, such as param
to indicate which parameter was missing or invalid. These fields are not guaranteed to be present outside of the error code they are documented for.
internal_server_error
internal_server_error
Internal server error is returned when an unknown, internal error happened. It is recommended to contact LootLocker support with the request id and trace id if this error persists.
Example:
parameter_missing
parameter_missing
Parameter missing is returned when a parameter required for the request is missing.
Example:
parameter_invalid
parameter_invalid
Parameter invalid is returned when a parameter required for the request is invalid.
Example:
request_body_invalid
request_body_invalid
Request body invalid is returned when the request body is invalid. This can be because the request body is empty or it is not valid JSON.
Example:
expectation_not_met
expectation_not_met
Expectation not met is returned when the request is valid but does not meet the expectations of the endpoint. This can be because the request contains an invalid parameter, or because the state of the server does not reflect the action being taken.
Example:
transaction_insufficient_funds
transaction_insufficient_funds
The transaction_insufficient_funds
error code is triggered when a player attempts to perform an action that requires more virtual currency than they currently possess.
This error code is specifically returned when a player tries to make a purchase using in-game virtual currency and their balance is insufficient to complete the transaction.
Example:
insufficient_permissions
insufficient_permissions
The insufficient_permissions
error code is triggered when a user attempts to perform an action that requires a higher level of permissions than they currently possess.
Example:
Last updated