Errors and Status Codes
Find a list of common HTTP status codes and error responses returned by the TopMessage API. Use these codes to diagnose issues and troubleshoot errors effectively.
Success Status Codes
| Status Code | Meaning | Description |
|---|---|---|
| 200 | Success | The request was successful, and the response contains the requested data. |
| 201 | Resource Created | The message or resource was created successfully. |
| 202 | Accepted | The request has been received but not yet processed. Processing is in progress. |
| 204 | No Content | The request was successful, but there is no content to return to the response. |
Client Error Status Codes
| Status Code | Meaning | Description |
|---|---|---|
| 400 | Bad Request | The request could not be understood or was missing required parameters. |
| 401 | Unauthorized | The request requires user authentication or the provided credentials are invalid. |
| 402 | Payment Required | The request cannot be processed due to insufficient balance. |
| 403 | Access Denied | The server understood the request but refuses to authorize it. |
| 404 | Resource Not Found | The requested resource could not be found on the server. |
| 429 | Rate Limit Exceeded | The client has sent too many requests in a given amount of time. |
Server Error Status Codes
| Status Code | Meaning | Description |
|---|---|---|
| 500 | Server Error | The server encountered an unexpected condition that prevented it from fulfilling the request. |
| 501 | Not Implemented | The server does not support the functionality required to fulfill the request. |
| 502 | Bad Gateway | The server received an invalid response from an upstream server. |
| 503 | Service Unavailable | The server is currently unable to handle the request due to temporary overload or maintenance. |
| 504 | Gateway Timeout | The server did not receive a timely response from an upstream server. |