Error
Effective error handling is crucial for building a reliable and resilient Tulu Switch integration. This guide will walk you through understanding and handling errors that may occur during API interactions.
HTTP Status Codes
| Code | Type | Error | Description |
|---|---|---|---|
| 100 | Informational | Continue | The server has received the request headers and the client should proceed to send the request body. |
| 101 | Informational | Switching Protocols | The requester has asked the server to switch protocols and the server has agreed to do so. |
| 102 | Informational | Processing | This code indicates that the server has received and is processing the request, but no response is available yet. |
| 200 | Success | OK | The request has succeeded. |
| 201 | Success | Created | The request has been fulfilled and resulted in a new resource being created. |
| 202 | Success | Accepted | The request has been accepted for processing, but the processing has not been completed. |
| 203 | Success | Non-Authoritative Information | The server successfully processed the request, but is returning information that may be from another source. |
| 204 | Success | No Content | The server successfully processed the request and is not returning any content. |
| 205 | Success | Reset Content | The server successfully processed the request, but is not returning any content. The client should reset the document view. |
| 206 | Success | Partial Content | The server is delivering only part of the resource due to a range header sent by the client. |
| 207 | Success | Multi-Status | The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made. |
| 208 | Success | Already Reported | The members of a DAV binding have already been enumerated in a previous reply to this request, and are not being included again. |
| 226 | Success | IM Used | The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance. |
| 300 | Redirection | Multiple Choices | The request has more than one possible response. The user-agent or user should choose one of them. |
| 301 | Redirection | Moved Permanently | The URL of the requested resource has been changed permanently. The new URL is given in the response. |
| 302 | Redirection | Found | The server is responding to the request with a temporary redirect to the URL given in the location header. |
| 303 | Redirection | See Other | The server is responding to the request with a redirect to a different URL, which should be retrieved using a GET method. |
| 304 | Redirection | Not Modified | The resource has not been modified since the last request, so no content is returned. |
| 305 | Redirection | Use Proxy | The requested resource is only available through a proxy, whose address is provided in the response. |
| 307 | Redirection | Temporary Redirect | The server is responding to the request with a temporary redirect to the URL given in the location header, using the same method as the original request. |
| 308 | Redirection | Permanent Redirect | The server is responding to the request with a redirect to a different URL, which should be retrieved using the same method as the original request. |
| 400 | Client Error | Bad Request | The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing). |
| 401 | Client Error | Unauthorized | The request has not been applied because it lacks valid authentication credentials for the target resource. |
| 402 | Client Error | Payment Required | Reserved for future use. The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, as proposed, for example, by GNU Taler, but that has not yet happened, and this code is not usually used. |
| 403 | Client Error | Forbidden | The server understood the request but refuses to authorize it. |
| 404 | Client Error | Not Found | The requested resource could not be found but may be available in the future. |
| 405 | Client Error | Method Not Allowed | A request method is not supported for the requested resource. |
| 406 | Client Error | Not Acceptable | The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request. |
| 407 | Client Error | Proxy Authentication Required | The client must first authenticate itself with the proxy. |
| 408 | Client Error | Request Timeout | The server timed out waiting for the request. |
| 409 | Client Error | Conflict | The request could not be completed due to a conflict with the current state of the target resource. |
| 410 | Client Error | Gone | The requested resource is no longer available and will not be available again. |
| 411 | Client Error | Length Required | The request did not specify the length of its content, which is required by the requested resource. |
| 412 | Client Error | Precondition Failed | The server does not meet one of the preconditions that the requester put on the request. |
| 413 | Client Error | Payload Too Large | The request is larger than the server is willing or able to process. |
| 414 | Client Error | URI Too Long | The URI provided was too long for the server to process. |
| 415 | Client Error | Unsupported Media Type | The server does not support the media type transmitted in the request. |
| 416 | Client Error | Range Not Satisfiable | The client has asked for a portion of the file, but the server cannot supply that portion. |
| 417 | Client Error | Expectation Failed | The server cannot meet the requirements of the Expect request-header field. |
| 418 | Client Error | I'm a Teapot | The server refuses the attempt to brew coffee with a teapot. |
| 421 | Client Error | Misdirected Request | The request was directed at a server that is not able to produce a response. |
| 422 | Client Error | Unprocessable Entity | The request was well-formed but was unable to be followed due to semantic errors. |
| 423 | Client Error | Locked | The resource that is being accessed is locked. |
| 424 | Client Error | Failed Dependency | The request failed because it depended on another request and that request failed. |
| 425 | Client Error | Too Early | The server is unwilling to risk processing a request that might be replayed. |
| 426 | Client Error | Upgrade Required | The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol. |
| 428 | Client Error | Precondition Required | The origin server requires the request to be conditional. |
| 429 | Client Error | Too Many Requests | The user has sent too many requests in a given amount of time. |
| 431 | Client Error | Request Header Fields Too Large | The server is unwilling to process the request because its header fields are too large. |
| 451 | Client Error | Unavailable For Legal Reasons | The server is denying access to the resource as a consequence of a legal demand. |
| 500 | Server Error | Internal Server Error | The server encountered an unexpected condition that prevented it from fulfilling the request. |
| 501 | Server Error | Not Implemented | The server does not support the functionality required to fulfill the request. |
| 502 | Server Error | Bad Gateway | The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request. |
| 503 | Server Error | Service Unavailable | The server is currently unable to handle the request due to a temporary overload or maintenance of the server. |
| 504 | Server Error | Gateway Timeout | The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI or some other auxiliary server it needed to access in order to complete the request. |
| 505 | Server Error | HTTP Version Not Supported | The server does not support, or refuses to support, the major version of HTTP that was used in the request message. |
| 506 | Server Error | Variant Also Negotiates | Transparent content negotiation for the request results in a circular reference. |
| 507 | Server Error | Insufficient Storage | The server is unable to store the representation needed to complete the request. |
| 508 | Server Error | Loop Detected | The server detected an infinite loop while processing the request. |
| 510 | Server Error | Not Extended | Further extensions to the request are required for the server to fulfill it. |
| 511 | Server Error | Network Authentication Required | The client needs to authenticate to gain network access. |
Contact Us for Developer Support
Contact our dedicated developer support team for assistance, guidance, or any questions you have regarding Tuluswitch API integration. We're here to ensure your development experience is smooth and successful.
Read Our Developer Blog for Insights
Master the Tuluswitch API with our Developer Blog! Get expert insights, advanced tips, and industry trends beyond the documentation. Stay connected with the developer community to build exceptional payment platforms. Visit the blog now and unlock your full potential!