How are sent messages and error codes?
Errors are retrieved using standard HTTP error code syntax. Any additional info is included in the body of the return call in JSON format.
Error codes that are not listed here can be found in the eRanker REST API functions documentation.
{
"status": "401",
"msg": "Bad or expired API Key.",
"solution": "To fix this make sure you api key.",
"command": "/report/[email protected]&apikey=92a06a967cc8a6c96as560ec5570bb2e91",
"time": "2015-04-13 20:43:07",
"debug": {
"line": 36,
"file": "checksession.php",
"lastsqlerror": null,
"rawphpinput": ""
}
}
Error Example
JSON-formatted error
Standard API errors
| Http/Api error code | Description |
|---|---|
| 400 | Bad input parameter. Error message should indicate which one and why. |
| 403 | Bad API Key. Re-authenticating the user won't help here. Your key may have been mistyped or you do not have access to our API. |
| 404 | File or folder not found at the specified path. |
| 405 | Request method not expected. |
| 503 | Your app is making too many requests and is being rate limited. 503s can trigger on a per-IP or per-user basis. |
| 507 | User has no credits left. |
| 5xx | Internal server error. |