Skip to main content

Account Operations

Below section describes error response codes from Client-API for different account services like ledger, restructure etc.

  1. Error Response: POST/v1/{clientId}/match_account_payment
HTTP Status CodeMeaningResolution TipError Response
400 Bad RequestMissing values in JSON payload-Check mandatory fields are part of payload -Mandatory values are 1. currency 2. totalAmount 3. matchStrategy 4. accountReference{"messages":["body/['<entityId>'] should have required property '<field>'"],"messageIds":[],"success":false}
400 Bad RequestWrong values in JSON payloadCheck enumerated value for -matchStrategy → * ORDERED_LEDGER_ENTRIES * ORDERED_INVOICES_WITH_FEES_THEN_ACCOUNT_ENTRIES * ACCOUNT_ENTRIES_THEN_ORDERED_INVOICES_WITH_FEES * CUSTOM_ORDERED_FEES
200 OK Transaction status: failedInvalid ID/s-Entity is wrong. Check the field mentioned for invalid resource 1. accountReference
  1. Error Response: POST/v1/{clientId}/restructure_account_overdue_invoices
HTTP Status CodeMeaningResolution TipError Response
400 Bad RequestMissing values in JSON payload-Check mandatory fields are part of payload -Mandatory values are 1. amounts 2. frequency → days + weeks + months 3. intialDueDate 4. accountReference{"messages":["body/['<entityId>'] should have required property '<field>'"],"messageIds":[],"success":false}
200 OK Transaction status: failedInvalid ID/s-Entity is wrong. Check the field mentioned for invalid resource 1. accountReference
  1. Error Response: POST/v1/{clientId}/discard_restructure_account_overdue_invoices
HTTP Status CodeMeaningResolution TipError Response
400 Bad RequestMissing values in JSON payload-Check mandatory fields are part of payload -Mandatory values are 1. accountReference{"messages":["body/['<entityId>'] should have required property '<field>'"],"messageIds":[],"success":false}
200 OK Transaction status: failedInvalid ID/s-Entity is wrong. Check the field mentioned for invalid resource 1. accountReference
  1. Error Response: POST/v1/{clientId}/resolve_restructure_account_overdue_invoices
HTTP Status CodeMeaningResolution TipError Response
400 Bad RequestMissing values in JSON payload-Check mandatory fields are part of payload -Mandatory values are 1. accountReference{"messages":["body/['<entityId>'] should have required property '<field>'"],"messageIds":[],"success":false}
200 OK Transaction status: failedInvalid ID/s-Entity is wrong. Check the field mentioned for invalid resource 1. accountReference
  1. Error Response: POST/v1/{clientId}/request_account_discount
HTTP Status CodeMeaningResolution TipError Response
400 Bad RequestMissing values in JSON payload-Check header fields are part of payload Mandatory values are 1. accountReference -Check JSON fields are part of payload Mandatory values are 1. discounts → type 2. discounts → current 3. discounts → discount 4. discounts → discountApplied 5. discounts → ledgerEntryReference{"messages":["body/['<entityId>'] should have required property '<field>'"],"messageIds":[],"success":false}
200 OK Transaction status: failedInvalid ID/s-Entity is wrong. Check the field mentioned for invalid resource 1. accountReference
  1. Error Response: GET/v1/{clientId}/get_account_discount_requests
HTTP Status CodeMeaningResolution TipError Response
400 Bad RequestMissing values in JSON payload-Check header fields are part of payload Mandatory values are 1. accountReference{"messages":["body/['<entityId>'] should have required property '<field>'"],"messageIds":[],"success":false}
200 OK Transaction status: failedInvalid ID/s-Entity is wrong. Check the field mentioned for invalid resource 1. accountReference
  1. Error Response: POST/v1/{clientId}/discard_account_discount
HTTP Status CodeMeaningResolution TipError Response
400 Bad RequestMissing values in JSON payload-Check fields are part of payload Mandatory values are 1. accountReference 2. discountIds{"messages":["body/['<entityId>'] should have required property '<field>'"],"messageIds":[],"success":false}
200 OK Transaction status: failedInvalid ID/s-Entity is invalid. Check the field mentioned for invalid resource 1. accountReference 2. discountIds
  1. Error Response: POST/v1/{clientId}/resolve_account_discount
HTTP Status CodeMeaningResolution TipError Response
400 Bad RequestMissing values in JSON payload-Check fields are part of payload Mandatory values are 1. accountReference 2. discountId{"messages":["body/['<entityId>'] should have required property '<field>'"],"messageIds":[],"success":false}
200 OK Transaction status: failedInvalid ID/s-Entity is invalid. Check the field mentioned for invalid resource 1. accountReference 2. discountId
  1. Error Response: POST/v1/{clientId}/prolong_account_outstanding_invoices
HTTP Status CodeMeaningResolution TipError Response
400 Bad RequestMissing values in JSON payload-Check fields are part of payload Mandatory values are 1. accountReference 2. days{"messages":["body/['<entityId>'] should have required property '<field>'"],"messageIds":[],"success":false}
200 OK Transaction status: failedInvalid ID/s-Entity is invalid. Check the field mentioned for invalid resource 1. accountReference
  1. Error Response: POST/v1/{clientId}/discard_prolong_account_outstanding_invoices
HTTP Status CodeMeaningResolution TipError Response
400 Bad RequestMissing values in JSON payload-Check fields are part of payload Mandatory values are 1. accountReference 2. prolongationClaimReferences{"messages":["body/['<entityId>'] should have required property '<field>'"],"messageIds":[],"success":false}
200 OK Transaction status: failedInvalid ID/s-Entity is invalid. Check the field mentioned for invalid resource 1. accountReference 2. prolongationClaimReferences
  1. Error Response: POST/v1/{clientId}/resolve_prolong_account_outstanding_invoices
HTTP Status CodeMeaningResolution TipError Response
400 Bad RequestMissing values in JSON payload-Check fields are part of payload Mandatory values are 1. accountReference 2. prolongationClaimRef{"messages":["body/['<entityId>'] should have required property '<field>'"],"messageIds":[],"success":false}
200 OK Transaction status: failedInvalid ID/s-Entity is invalid. Check the field mentioned for invalid resource 1. accountReference 2. prolongationClaimRef
  1. Error Response: GET/v1/{clientId}/get_account_mandates
HTTP Status CodeMeaningResolution TipError Response
400 Bad RequestMissing values in JSON payload-Check url params fields are part of payload Mandatory values are 1. accountReference{"message": "Missing required request parameters: [accountReference]"}
200 OK Empty response payloadInvalid ID/s-Entity is wrong. Check the field mentioned for invalid resource 1. accountReferenceEmpty response []
  1. Error Response: POST/v1/{clientId}/set_account_prolongation _fee_strategy
HTTP Status CodeMeaningResolution TipError Response
400 Bad RequestMissing values in JSON payload-Check fields are part of payload Mandatory values are 1. prolongationFeeStrategyConditions → amount/lessOrEqualToDays{"messages":["body/['<entityId>'] should have required property '<field>'"],"messageIds":[],"success":false}
  1. Error Response: GET/v1/{clientId}/get_account_prolongation_requests
HTTP Status CodeMeaningResolution TipError Response
400 Bad RequestMissing values in JSON payload-Check url params fields are part of payload Mandatory values are 1. accountReference{"message": "Missing required request parameters: [accountReference]"}
200 OK Empty response payloadInvalid ID/s-Entity is wrong. Check the field mentioned for invalid resource 1. accountReferenceEmpty response []