---
title: "List disputes"
method: GET
path: "/v1/disputes"
tags: ["Disputes"]
---

# List disputes

`GET /v1/disputes`

Get disputes with paging and filter options.

## Query parameters

- `beginDate` string
- `endDate` string
- `page` integer
- `perPage` integer
- `accountId` integer
- `isNetwork` boolean
- `isDisputeMigrated` boolean
- `isDisputeInvalidTransaction` boolean
- `group` 'OPEN' | 'APPROVED' | 'DENIED' | 'CARDNETWORK_CHARGEBACK' | 'ANALYSING' | 'CARDNETWORK_SECOND_PRESENTMENT' | 'FAILED' | 'CARDNETWORK_PREARBITRATION' | 'RESEND' | 'LOSS' | 'WON' | 'REJECTED' | 'FAILED_PROCESSED'
- `status` 'OPENED' | 'PENDING' | 'CANCELED' | 'FAILED' | 'CHARGEBACK_REJECTED' | 'CHARGEBACK_CREATED' | 'CHARGEBACK_ACCEPTED' | 'CHARGEBACK_CLOSED' | 'SECOND_PRESENTMENT' | 'PRE_ARBITRATION_OPENED' | 'PRE_ARBITRATION_ACCEPTED' | 'PRE_ARBITRATION_DECLINED' | 'PRE_ARBITRATION_RECALL' | 'PRE_ARB_ALLOCATION_OPENED' | 'FAILED_PRE_ARBITRATION' | 'PRE_ARB_ALLOCATION_ACCEPTED' | 'PRE_ARB_ALLOCATION_DECLINED' | 'PRE_ARB_ALLOCATION_RECALLED' | 'FAILED_DECLINE_PRE_ARB' | 'FAILED_ACCEPT_PRE_ARB' | 'FAILED_ON_CLOSE' | 'EXPIRED' | 'ISSUER_LOSS' | 'MIGRATION' | 'FAILED_MIGRATION'

## Headers

- `Authorization` string, required

## Response `200`

OK

- FullDisputeResponse[]
  - `id` number — Dispute ID
  - `org_id` string — Organization ID
  - `account_id` integer — Account ID
  - `authorization_id` integer — Authorization ID.
  - `disputed_amount` number — Disputed amount.
  - `comment` string, nullable — Client custom dispute comment. **REQUIRED** for Visa partial dispute to explain why partial.
  - `airport_tax` boolean — For ELO card network, should dispute for airport tax be created? Default is `true` for ELO.
  - `airport_tax_partial` boolean — For ELO card network, should airport tax be partially disputed? Default is `false`.
  - `airport_tax_amount` number — Airport tax amount to be disputed. **REQUIRED** if `airport_tax_partial` is `true`.
  - `dispute_reason` number — Each card network, such as Visa or Mastercard, defines and maintains their own unique set of reason codes, which banks that issue credit and debit cards under their brands apply to disputes. Here's a reason code [quick reference](https://www.chargebackgurus.com/blog/a-definitive-guide-to-chargeback-reason-codes-by-card-network#chargback-reason-code-quick-reference-guide) for the major credit card networks. For Visa, this would be either `10` (fraud - card present), `11` (authorization), `12` (processing error), or `13` (consumer dispute). For more infomation, refer to the [Visa](https://usa.visa.com/dam/VCOM/global/support-legal/documents/chargeback-management-guidelines-for-visa-merchants-vbs-19-may-16-%20v2.pdf) or [Mastercard](https://www.mastercard.us/content/dam/public/mastercardcom/na/global-site/documents/chargeback-guide.pdf) chargeback quides. For example - `4853` (Mastercard - cardholder dispute), `12` (Visa - processing error) or `72` (ELO - denied authorization)
  - `modality` number — Dispute *modality* - legacy term for reason code to file the dispute.
  - `dispute_status` 'OPENED' | 'PENDING' | 'CANCELED' | 'FAILED' | 'CHARGEBACK_REJECTED' | 'CHARGEBACK_CREATED' | 'CHARGEBACK_ACCEPTED' | 'CHARGEBACK_CLOSED' | 'SECOND_PRESENTMENT' | 'PRE_ARBITRATION_OPENED' | 'PRE_ARBITRATION_ACCEPTED' | 'PRE_ARBITRATION_DECLINED' | 'PRE_ARBITRATION_RECALL' | 'PRE_ARB_ALLOCATION_OPENED' | 'FAILED_PRE_ARBITRATION' | 'PRE_ARB_ALLOCATION_ACCEPTED' | 'PRE_ARB_ALLOCATION_DECLINED' | 'PRE_ARB_ALLOCATION_RECALLED' | 'FAILED_DECLINE_PRE_ARB' | 'FAILED_ACCEPT_PRE_ARB' | 'FAILED_ON_CLOSE' | 'EXPIRED' | 'ISSUER_LOSS' | 'MIGRATION' | 'FAILED_MIGRATION' — Dispute status enums.
  - `dispute_group_status` 'OPEN' | 'APPROVED' | 'DENIED' | 'CARDNETWORK_CHARGEBACK' | 'ANALYSING' | 'CARDNETWORK_SECOND_PRESENTMENT' | 'FAILED' | 'CARDNETWORK_PREARBITRATION' | 'RESEND' | 'LOSS' | 'WON' | 'REJECTED' | 'FAILED_PROCESSED' — Group status enums
  - `timeline` string — Client custom timeline information.
  - `protocol` string — Client custom protocol ID. This is primarily for you to internally identify a request. If not provided, Pismo creates a CID (correlation ID) field for this purpose.
  - `metadata` string — Any data object with key/value pairs. No limit on length. **Note**: This field must not be used to send Personally Identifiable Information (PII), Payment Card Industry (PCI) data, or any sensitive/regulated information. Metadata fields are intended for operational, non-sensitive data only. For sensitive data, use the specific parameters designed for that purpose. For more information, refer to [Get started with Pismo APIs](https://developers.pismo.io/pismo-docs/reference/get-started-with-pismo-apis#metadata).
  - `created_at` string, date-time — Datetime program calendar strategy was created. Format = YYYY-MM-DDTHH:MM:SS:MM.
  - `updated_at` string, date — Dispute last updated date, format = yyyy-mm-dd.
  - `created_at_utc` string, date-time — Dispute created in UTC date/time.
  - `updated_at_utc` string — When dispute updated in UTC date/time.
  - `is_network` boolean — Open a dispute over a network authorization.
  - `is_dispute_migrated` boolean — Has this dispute been migrated to the Pismo platform?
  - `reversal_id` number — Dispute credit reversal ID.
  - `network_return_reason_code` string — Network reason code response.
  - `network_brand_type` 'Visa' | 'Mastercard' | 'Elo' — Network brand
  - `transaction_date` string — Transaction date related to authorization, format = yyyy-mm-dd
  - `stop_automated_installment` boolean — Automated dispute installment control flag. If an issuer opens a dispute for a transaction that has more than one installment, with installments that can still be posted, the issuer will need to open a dispute for subsequent installments as well. With automated dispute installment control, once you open a chargeback for the first installment, the same information can be used for subsequent transaction installments.
  - `card_hash` string — Card number hash.
  - `authorization_code` string — Authorization code
  - `transaction_amount` number — Transaction amount
  - `is_dispute_invalid_transaction` boolean — Is this an invalid authorization dispute?

## Other responses

- `400` — Bad request
- `401` — Access token is missing or invalid
- `500` — Internal server error

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/revisions/935b62e16de4/schema)