Errors
In this guide, we will discuss what happens when something goes wrong while using the API. Errors do happen, and most of them are yours, not ours. Let's look at some status codes and error types you might encounter.
You can determine if a request was successful by checking the status code when you receive an API response. If the response returns unsuccessful, you can use the error type and error message to find out what went wrong and do some basic debugging (before contacting support).
Before contacting support about an error, please note that 99% of reported errors are actually user errors. Therefore, please carefully check your code before contacting eopen.io support.
Status codes
Below is a list of different categories of status codes returned by the eopen.io API. Use these to understand if your request was successful.
- Name
0- Description
- Status code indicates the response was successful
- Name
100- Description
- Request parameter error
- Name
11000- Description
- Operation failed, please try again later
- Name
11001- Description
- Operations too frequent
- Name
11003- Description
- Missing required parameters
- Name
12002- Description
- Order does not exist
- Name
20000- Description
- Application does not exist
- Name
20001- Description
- Invalid API key
- Name
20002- Description
- Insufficient account balance
- Name
20003- Description
- Insufficient quota
- Name
20004- Description
- Request frequency limited
- Name
20005- Description
- Invalid receiving address
- Name
20006- Description
- Invalid energy parameter
- Name
20007- Description
- Invalid staking amount
- Name
20008- Description
- Invalid rental duration
- Name
20009- Description
- Insufficient remaining resources
- Name
20010- Description
- Invalid time unit, only h/d supported
- Name
20011- Description
- Invalid parameter
- Name
20012- Description
- IP not in whitelist
Error types
Whenever a request is unsuccessful, the eopen.io API will return an error response containing an error type and message. You can use this information to better understand what went wrong and how to fix it. Most error messages are very helpful and actionable.
Error response
{
"code": 100,
"msg": "Request parameter error",
"time":1737195360794,
"data": {}
}