5. Handle Error

RemitPro uses standard HTTP response codes to communicate the status of API requests. It is expected that API consumers manage these codes and messages effectively to ensure efficient error handling and uninterrupted transaction flow.

5.1 Anatomy of Error Response

Field	Data Type	Description
status	Integer	Standard HTTP status code indicating the result of the request. Examples: `200 for success`, `400 for Bad Request`, `401 for Unauthorized`, `500 for Internal Server Error.`
serviceStatus	String	A system-specific status code that offers a more granular classification of the error within the service. This code helps developers quickly identify and troubleshoot the exact issue in the system’s error catalog.
titleCode	String	A short, machine-readable error identifier used to categorize the type of problem.
title	String	A brief, human-readable summary of the error type, meant to be easily understood without digging into technical logs.
detail	String	A detailed message describing the specific cause of the error. This field helps developers or API consumers understand exactly what input caused the issue, so they can correct and resubmit the request.
responseTime	String (ISO 8601)	The timestamp when the RemitPro system generated the response, in ISO 8601 format with timezone information. Useful for logging, auditing, and correlating logs.

Modified at 2025-08-15 09:20:32

4. Authorization & Scope