> ## Documentation Index
> Fetch the complete documentation index at: https://docs.shoply.gg/llms.txt
> Use this file to discover all available pages before exploring further.

# List an order's disputes

> The disputes on one order, newest first, each as List disputes has it. Most orders have none; a payment disputed twice has two.

Needs the `disputes.read` permission (Read Disputes).



## OpenAPI

````yaml /api-reference/openapi.json get /stores/{storeId}/orders/{orderId}/disputes
openapi: 3.1.0
info:
  title: Shoply API
  version: '1'
  description: >-
    Everything a store's own server can do with a secret API key: its catalogue,
    orders, customers, marketing, finance and the rest of what the dashboard
    does. And the Customer API, which a buyer's own device asks with a token of
    theirs.
servers:
  - url: https://api.shoply.gg/v1
security:
  - apiKey: []
tags:
  - name: API key
  - name: Store
  - name: Domain
  - name: Payment methods
  - name: Analytics
  - name: Storefronts
  - name: Storefront code
  - name: Payment Routing
  - name: Custom payment methods
  - name: Products
  - name: Product pictures
  - name: Stock
  - name: Categories
  - name: Upsells
  - name: Subscriptions
  - name: Orders
  - name: Invoices
  - name: Reviews
  - name: Coupons
  - name: Coupon categories
  - name: Coupon pop-up
  - name: Sales
  - name: Blog
  - name: Search settings
  - name: Redirects
  - name: Sitemap
  - name: Cart Recovery
  - name: Email Marketing
  - name: Email Templates
  - name: Customers
  - name: Affiliates
  - name: Support Tickets
  - name: Blacklist
  - name: Fraud protection
  - name: Disputes
  - name: Finance
  - name: Tax
  - name: Expenses
  - name: Expense setup
  - name: API requests
  - name: Webhook endpoints
  - name: Webhook deliveries
  - name: Customer API
paths:
  /stores/{storeId}/orders/{orderId}/disputes:
    get:
      tags:
        - Disputes
      summary: List an order's disputes
      description: >-
        The disputes on one order, newest first, each as List disputes has it.
        Most orders have none; a payment disputed twice has two.


        Needs the `disputes.read` permission (Read Disputes).
      operationId: disputes.forOrder
      parameters:
        - name: storeId
          in: path
          required: true
          description: >-
            The store's ID. A key reaches the store it was made in: `GET /key`
            answers which.
          schema:
            type: string
        - name: orderId
          in: path
          required: true
          description: The order, by its ID.
          schema:
            type: string
      responses:
        '200':
          description: It worked.
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                  message:
                    nullable: true
                  code:
                    nullable: true
                  data:
                    type: array
                    items:
                      type: object
                      properties:
                        id:
                          type: string
                        orderId:
                          type: string
                        email:
                          type: string
                        provider:
                          type: string
                        providerName:
                          type: string
                        externalId:
                          type: string
                        reason:
                          type: string
                        reasonText:
                          type: string
                        stage:
                          type: string
                        providerStatus:
                          type: string
                        status:
                          type: string
                        amount:
                          type: integer
                        currency:
                          type: string
                        dueAt:
                          type: string
                        answer:
                          type: object
                          properties:
                            state:
                              type: string
                            at:
                              nullable: true
                            by:
                              type: string
                            note:
                              type: string
                        answeredFrom:
                          type: string
                        answerPlace:
                          type: string
                        accessTaken:
                          type: boolean
                        dateCreated:
                          type: string
                        dateClosed:
                          nullable: true
              example:
                success: true
                message: null
                code: null
                data:
                  - id: ae36fc25-3cea-4d17-acaa-4bdb43d84a0e
                    orderId: 71ed606f-3119-4f9f-b7f7-ecd25740e15b
                    email: mila@example.com
                    provider: stripe
                    providerName: Stripe
                    externalId: dp_1QdZ8x2eZvKYlo2C
                    reason: fraudulent
                    reasonText: Says they did not make the payment
                    stage: chargeback
                    providerStatus: needs_response
                    status: needs_response
                    amount: 49
                    currency: USD
                    dueAt: '2026-10-27T16:20:19Z'
                    answer:
                      state: ''
                      at: null
                      by: ''
                      note: ''
                    answeredFrom: provider
                    answerPlace: your Stripe Dashboard
                    accessTaken: false
                    dateCreated: '2026-10-22T16:20:19Z'
                    dateClosed: null
        '401':
          $ref: '#/components/responses/NoKey'
        '403':
          $ref: '#/components/responses/NotAllowed'
        '404':
          $ref: '#/components/responses/NotFound'
        '429':
          $ref: '#/components/responses/TooMany'
      x-codeSamples:
        - lang: javascript
          label: Node.js
          source: |
            import Shoply from "@shoplygg/node";

            const shoply = new Shoply({ apiKey: process.env.SHOPLY_API_KEY });

            const result = await shoply.disputes.forOrder("ORDER_ID");
        - lang: php
          label: PHP
          source: |
            <?php

            require 'vendor/autoload.php';

            $shoply = new Shoply\Client(['apiKey' => getenv('SHOPLY_API_KEY')]);

            $result = $shoply->disputes->forOrder('ORDER_ID');
        - lang: python
          label: Python
          source: |
            import shoply

            client = shoply.Client()  # reads SHOPLY_API_KEY

            result = client.disputes.forOrder("ORDER_ID")
components:
  responses:
    NoKey:
      description: >-
        No API key was sent, or the one sent is not a live key:
        `api_key_required`, `invalid_api_key`.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Refusal'
    NotAllowed:
      description: >-
        The key is real and may not do this: `missing_scope` (with
        `requiredScope`), `ip_not_allowed`, `account_unavailable`, or
        `dashboard_only` for something only a person in the dashboard may do.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Refusal'
    NotFound:
      description: >-
        There is no such thing in this store: `not_found`. A store that is not
        the key's own is answered the same way.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Refusal'
    TooMany:
      description: >-
        The key has used up its budget for now: `rate_limited`. `Retry-After`
        says how many seconds to wait.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Refusal'
  schemas:
    Refusal:
      type: object
      properties:
        success:
          type: boolean
          example: false
        message:
          type: string
          description: What is wrong, in words for a person.
        code:
          type: string
          description: What is wrong, as a word that does not change.
        data:
          nullable: true
        errors:
          type: object
          description: >-
            For `validation_failed`: what is wrong with each field, by the
            field's name.
          additionalProperties:
            type: string
      required:
        - success
        - message
        - code
  securitySchemes:
    apiKey:
      type: http
      scheme: bearer
      description: >-
        A secret API key, made under Developers in the dashboard:
        `Authorization: Bearer shoply_sk_...`

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.