RemitPro - API International Remittance
  1. Getting Strated Guide
RemitPro - API International Remittance
  • Getting Strated Guide
    • 1. Overview
    • 2. High Level Flow
    • 3. Supported Corridors
    • 4. Authorization & Scope
    • 5. Handle Error
    • 6. Signature
    • 7. API Host
    • 8. Doc Change Log
  • API Reference (V1)
    • Authentication
      • Generate Token
        POST
      • Refresh Token
        POST
    • Master Data
      • Onboarding
        • Overview
        • Id Type Personal
        • Id Types Business
        • Business Classification
        • Business Industry
        • Nature of Business
        • Business Entity
        • Document Types Personal
        • Document Types Business
        • Education
        • Gender
        • Marital Status
        • Nationalities
        • Occupation
        • Purpose Account
        • Salutation
        • User Position
      • Area
        • Overview
        • Countries
        • Countries by Id
        • States
        • States by Id
        • City
        • City by Id
        • District
        • District by Id
        • Sub District
        • Sub District by Id
      • Transaction
        • Overview
        • Bank
        • Bank Branch
        • Bank Account Type
        • Business Classification
        • Business Industry
        • Nature of Business
        • Business Entity
        • Identity Types
        • Education
        • Gender
        • Marital Status
        • Nationalities
        • Occupation
        • Phone Prefix
        • Purpose of Payment
        • Recipient of Relationship
        • Source of Income
        • User Position
        • Work Status
    • Payout Cross Border
      • Sender
        • Business
          • Create Sender
          • Update Sender
          • Deactive
          • Reactive
          • Sender Detail
          • Sender List
          • History List
        • Personal
          • Create Sender
          • Update Sender
          • Deactive
          • Reactive
          • Sender Detail
          • Sender List
          • History List
      • Recipient
        • Overview
        • Business
          • Recipient Form
          • Create
          • Update
          • Deactive
          • Reactive
          • Recipient Detail
          • Recipient List
          • History List
        • Personal
          • Recipient Form
          • Create
          • Update
          • Deactive
          • Reactive
          • Recipient Detail
          • Recipient List
          • History List
      • Quotes
        • Enquire Quotes
        • Quote List
        • Quote Detail
      • Transaction
        • Create Transaction
        • Transaction Status
        • Transaction List
        • Transaction Detail
    • Onbording Member
      • Business
        • Get Business Document
        • Create Member
        • Update
        • Deactive
        • Reactive
        • Member List
        • Member Detail
        • History List
      • Personal
        • Create Member
        • Update
        • Deactive
        • Reactive
        • Member List
        • Member Detail
        • History List
    • Wallet
      • Overview
      • Own Wallet
      • Wallet Member List
      • Detail Wallet Member
      • Wallet Histories
    • Virtual Account
      • Create Virtual Account
      • Virtual Account List
      • Virtual Account Detail
      • Top Up Simulation
    • Webhook
      • Overview
      • Webhook Category
      • Create Webhook URL
      • Webhook URL List
      • Update
      • Deactive
  1. Getting Strated Guide

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#

FieldData TypeDescription
statusIntegerStandard 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.
serviceStatusStringA 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.
titleCodeStringA short, machine-readable error identifier used to categorize the type of problem.
titleStringA brief, human-readable summary of the error type, meant to be easily understood without digging into technical logs.
detailStringA 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.
responseTimeString (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.

5.2 List of Status Codes#

StatusExplanationExpected handling
200API request was successfulRequest processed successfully.
400Invalid Request Parameters- Validate client-side input before retrying.
- Fix incorrect or missing request parameters.
- Return or display a clear error message to the user.
401Unauthorized access- Check authentication token/credentials.
-If the token is expired,refresh or re-authenticate.
- Inform the user that authorization is required.
403Forbidden access- Do not retry automatically.
- Verify user role/permissions.
- Return an appropriate error message (“Access denied”).
404Resource not found- Ensure the endpoint or resource path is correct.
- If the resource truly doesn’t exist, return a “Not Found” error.
- Do not retry automatically.
409Conflict- Handle conflict (e.g., duplicate record, concurrent modification).
- Notify the user that the operation failed due to a conflict.
- Require client to resolve conflict before retrying.
500Internal server error- Error originates from the server, not the client.
- Show a generic error message: “Something went wrong. Please try again later.”
- Do not retry continuously; apply exponential backoff if retrying.
Log and monitor the error for investigation.
Modified at 2025-09-22 12:37:12
Previous
4. Authorization & Scope
Next
6. Signature
Built with