API Response Codes
To ensure successful communication, the sending system must verify a successful API or web service response code.
It is the sender’s responsibility to verify that each API call receives a successful 200 level response. Below is an excerpt from https://developer.mozilla.org and [https://restfulapi.net/http-status-codes/]
Web API’s typically use the Status-Line section of an HTTP response message to inform clients of their request’s overarching result.
HTTP defines these standard status codes that can be used to convey the results of a client’s request. The status codes are divided into the five categories:
• 1xx: Informational – Communicates transfer protocol-level information.
• 2xx: Success – Indicates that the client’s request was accepted successfully.
• 3xx: Redirection – Indicates that the client must take some additional action in order to complete their request.
• 4xx: Client Error – This category of error status codes points the finger at clients.
• 5xx: Server Error – The server takes responsibility for these error status codes.
As with all API communications, it is the responsibility of the sending system to ensure that every call receives a successful 200 level response. Spring Systems does not log non successful transactions.
Examples of successful transactions:
Examples of failed transactions:
Example 1 - Postman tool displays a response code as follows:
Example 2 - This is how it looks like on raw api call, the code is in response, how to find and interpret the code depends on the system that sent the request.