# Response Code

## HTTP Response Code

Udara360 relies on standard HTTP response codes to signify the success or failure of API requests. A successful request will result in an HTTP status code of 200. Refer to the response code list below if troubleshooting is required, and double-check your parameters for spelling errors to prevent issues.

| Description             | Code  |
| ----------------------- | ----- |
| Successful              | `2XX` |
| Bad request from client | `4XX` |
| System error            | `5XX` |

## Postings Response code

When using the Transaction Posting API, it's crucial to understand the meaning of the posting response codes. Below is a list of all the response codes, along with their descriptions:

| Description                  | Code |
| ---------------------------- | ---- |
| Successful                   | `00` |
| General Error                | `06` |
| Model Validation Error       | `09` |
| Invalid Amount               | `13` |
| No Record Found              | `25` |
| Duplicate Record             | `26` |
| Force Debit Not Allowed      | `28` |
| Database Update Not Executed | `29` |
| Format Error                 | `30` |
| Insufficient Balance         | `51` |
| No Check Account             | `52` |
| Transaction Permission       | `57` |
| Security Violation           | `63` |
| Cut Off In Progress          | `90` |
| Exceeds Cash Limit           | `93` |
| Fatal Error                  | `96` |