General Error Pattern & Codes
Description
All HPM services use a standardized error structure compatible with the Finrota API architecture.
Common fields:
-
statusCode– Code representing the status of the operation (e.g., 200, 400, 401, 500, etc.) -
message– Human-readable summary message. -
errors/exceptions– Detailed list of errors or exception information (if any).
Common HTTP Codes
| Code | Meaning |
|---|---|
| 200 | OK → Operation successful, result returned. |
| 201 | Created → A new resource was created (not typical for HPM). |
| 400 | Bad Request → Required field missing, format error, etc. |
| 401 | Unauthorized → Token missing or invalid. |
| 403 | Forbidden → No service permission/license. |
| 404 | Not Found → Related record/resource not found. |
| 409 | Conflict → Conflicting state (e.g., scenarios related to the same clientOrderReference rule, etc.). |
| 422 | Unprocessable Entity → Validation errors (field-based). |
| 429 | Too Many Requests → Minute/request limits exceeded. |
| 500 | Internal Server Error → General server error. |
| 503 | Service Unavailable → Service temporarily unavailable. |