Error handling

400 Bad Request: Indicates that the server cannot process the request due to invalid syntax or a client-side error, such as incorrect input data or missing parameters.

401 Unauthorized: Denotes that access to the requested resource is restricted due to missing or invalid authentication credentials, like an expired or incorrect API key/token.

404 Not Found: Indicates that the requested wallet address does not exist on the server, often due to a wrong URL/path or an entity not being available.

429 Too Many Requests: Occurs when the user has sent too many requests within a specific time frame, exceeding the defined rate limits or throttling constraints.

500 Internal Server Error: Signifies an unexpected server-side error that prevents the server from fulfilling the request, often due to a programming or configuration issue.

503 Service Unavailable: Indicates that the server is temporarily unable to handle the request due to maintenance, overload, or unavailability of resources.

504 Gateway Timeout: Occurs when the server acting as a gateway or proxy does not receive a timely response from an upstream server, leading to a timeout in processing the request.

For further information or support on error messages, please join the Telegram group.