# Retrieve a dispute Retrieves a dispute with a specified ID. Endpoint: GET /disputes/{id} Version: latest Security: SecretApiKey, JWT ## Path parameters: - `id` (string, required) ID of the resource. ## Response 200 fields (application/json): - `id` (string) ID of the dispute. Example: "dp_0YVCE8J5F2DE58FV0S8YASW4HK" - `customerId` (string,null) ID of the customer who is disputing a transaction. Example: "cus_0YV7DDSDD1C8DA64KHH2W33CPF" - `transactionId` (string,null) ID of the disputed transaction. Example: "txn_0YVDTQJ8YWDGQACV2N2N5SPWQ0" - `currency` (string) Currency code in ISO 4217 format. - `amount` (number) Dispute amount. - `acquirerReferenceNumber` (string,null) Acquirer reference number for the dispute. - `caseId` (string,null) Case ID of the dispute. - `reasonCode` (string,null) Code used in the chargeback that describes the reason for the dispute. - `reasonDescription` (string,null) Description of the reason for the dispute. - `category` (string) Category of dispute. Enum: "fraud", "authorization", "processing-errors", "consumer-disputes", "uncategorized", "bank-return" - `type` (string) Type of dispute. Enum: "information-request", "first-chargeback", "second-chargeback", "arbitration", "fraud", "ethoca-alert", "verifi-alert", "bank-return", "paypal-claim", "representment", "inquiry", "forced-refund" - `status` (string) Status of the dispute. Enum: "response-needed", "under-review", "forfeited", "won", "lost", "unknown" - `postedTime` (string) Date and time when the dispute is posted. - `deadlineTime` (string,null) Latest date and time by when a merchant must submit a representment for a dispute. If the deadline is missed, the merchant loses the dispute. - `rawResponse` (string,null) Raw response from the payment gateway that processed the disputed transaction. - `resolvedTime` (string,null) Date and time when the dispute is resolved. - `source` (string,null) Source of the dispute. Enum: null, "api", "manual", "sftp", "webhook" - `revision` (integer) Number of times the dispute data has been modified. Use the revision number when analyzing webhook data to determine if a change should take precedence over the current representation. - `createdTime` (string) Date and time which is set automatically when the resource is created. - `updatedTime` (string) Date and time which updates automatically when the resource is updated. - `_links` (array) Related links. - `_links.href` (string) Link URL. - `_links.rel` (string) Type of link. Enum: "self", "transaction", "customer", "attachments" - `_embedded` (object) Embedded objects that are requested by the query parameter. - `_embedded.transaction` (object) - `_embedded.customer` (object) ## Response 401 fields (application/json): - `status` (integer) HTTP status code. - `type` (string) Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference. It should provide human-readable documentation for the problem type. When this member is not present, its value is assumed to be "about:blank". - `title` (string) Short, human-readable summary of the problem type. Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem. - `detail` (string) Human-readable explanation that is specific to this occurrence of the problem. - `instance` (string) URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced. ## Response 403 fields (application/json): - `status` (integer) HTTP status code. - `type` (string) Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference. It should provide human-readable documentation for the problem type. When this member is not present, its value is assumed to be "about:blank". - `title` (string) Short, human-readable summary of the problem type. Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem. - `detail` (string) Human-readable explanation that is specific to this occurrence of the problem. - `instance` (string) URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced. ## Response 404 fields (application/json): - `status` (integer) HTTP status code. - `type` (string) Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference. It should provide human-readable documentation for the problem type. When this member is not present, its value is assumed to be "about:blank". - `title` (string) Short, human-readable summary of the problem type. Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem. - `detail` (string) Human-readable explanation that is specific to this occurrence of the problem. - `instance` (string) URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.