Skip to main content

Dispute management response codes

This document outlines the response codes associated with the Dispute Management API. These codes are essential for understanding the status of API responses and are instrumental in diagnosing and resolving any issues that may arise from request submissions.

Relevant response fields

Besides httpStatus, the rest of the following fields are only included in the body of an unsuccessful response and can be helpful for troubleshooting purposes:

  • httpStatus: The response code that is returned to the client based on how a backend service handled the request.
  • title: Short human readable title of the error.
  • context: An array of objects for failed requests, comprising of the following fields:
    • code - The dispute managerment API employs the following numbering convention to indicate a specific type of issue:   
      • 10** - Invalid/Missing mandatory field errors / Validation Failures
      • 11** - Business Validation Failures
      • 12** - Timeouts
      • 13** - Other Errors
      • 15** - System Errors
      • 14** - Authentication/Authorization Failures
    • message - Provides textual description of a problem that has occurred.
    • field - The field for which the error has occured.
    • location - Location of the field for which the error occurred in the request ["BODY","PATH","QUERY","HEADER"]

Successful responses (200-299)

A 2XX httpStatus code signifies that a request has been successfully processed.

HTTP 2XX status codes
  httpStatus Scenario Relevant API endpoint(s)
  200 Successfully retrieved a list of disputes.
  • /disputes
  200 Successfully retrieved dispute details.
  • /disputes/{disputeId}
  200 Successfully retieved disputes status.
  • /disputes/status-query
  200 Successfully retieved a list of issuer documents. 
  • /disputes/{disputeId}/documents
  200 Successfully challenged a dispute.
  • /disputes/{disputeId}/challenge
  200 Successfully fulfilled a retrieval request.
  • /disputes/{disputeId}/fulfill
  200 Successfully accepted a dispute.
  • /disputes/{disputeId}/accept 

Client error responses (400-499)

A 4XX httpStatus code indicates that an error has occurred during a request, and provides a list of specific context code(s) and context message(s) to aid in troubleshooting. Address the problem and resubmit the request.

HTTP 4XX status codes

httpStatus

 context code

context message

 Relevant API endpoint(s)                                                       
400 11002 Document validation failed.
  • /disputes/{disputeId}/challenge
  • /disputes/{disputeId}/fulfill
  
400 11003 No document found.
  • /disputes/{disputeId}/challenge
  • /disputes/{disputeId}/fulfill
  
400 11001 Invalid document type provided.
  • /disputes/{disputeId}/challenge
  • /disputes/{disputeId}/fulfill
  
400 10001 At least one of the MerchantId, DisputeId, startDateTime or endDateTime is required to retrieve status.
  • /disputes/status-query
  
400 10102 Invalid Date range, either of the cases met. end date is prior to start date, start date or end date is future date.
  • /disputes/status-query
  
400 10001 Mandatory field missing or invalid.
  • All
  
400 10001 Invalid value for parameter.
  • All
  
400 10104 Unsupported value.
  • All
  
400 10908 Invalid request.
  • All
  
400 10105 Please enter valid required headers.
  • All
  
401 14000 Authentication Failure.
  • All
  
403 14001 Authorization Failure.
  • All
  
404 10107 The dispute case does not exist.
  • All
  
406 13007 Action not allowed on the dispute case.
  • /disputes/{disputeId}/challenge
  • /disputes/{disputeId}/fulfill
  • /disputes/{disputeId}/accept
  
422 10908 Invalid request
  • All
  

Server error responses (500-599)

A 5XX httpStatus code indicates that an error has occurred within the J.P. Morgan environment during the request. Additional fields are provided in the body of the response to identify the error.

HTTP 5XX status codes
httpStatus

context code 

context message

Relevant API endpoint(s)
503 12999 Service Unavailable.
  • All
503 13005 Service Unavailable.
  • /disputes/status-query
  • /disputes
503 13006 Service Unavailable.
  • /disputes/status-query
  • /disputes
503 13008 Service Unavailable.
  • /disputes/{disputeId}/challenge
  • /disputes/{disputeId}/fulfill
  • /disputes/{disputeId}/accept
    		•
    503 13009 Service Unavailable.
  • /disputes/{disputeId}/challenge
  • /disputes/{disputeId}/fulfill
  • /disputes/{disputeId}/accept
    		•
    503 13010 Service Unavailable.
  • /disputes/{disputeId}/challenge
  • /disputes/{disputeId}/fulfill
  • /disputes/{disputeId}/accept
    		•
    503 13011 Service Unavailable.
  • /disputes/{disputeId}/challenge
  • /disputes/{disputeId}/fulfill
    		•
    503 13012 Service Unavailable.
  • /disputes/{disputeId}/documents
    		•