List disputes
The disputes buyers opened on the store’s payments, as their payment providers reported them: the ones that need an answer first, soonest deadline first, then the rest newest first. status is how it reads on the dashboard: needs_response, under_review, won, lost, accepted or closed (ended with no chargeback). providerStatus is the provider’s own last word, stage is inquiry, chargeback, claim (a PayPal case), pre_arbitration or arbitration, and dueAt when the provider stops taking an answer, where it says. answeredFrom is where it is answered: here (through this API: Stripe’s, Revolut’s, Adyen’s, and PayPal’s where PayPal is connected with API keys), provider (in the provider’s own dashboard, named in answerPlace) or none. meta.figures is the dashboard’s four: how many need an answer and how many are due within three days, the money in the open ones in the store’s currency, how many ended won and lost in the last 90 days, and the orders disputed beside those that took money in that time.
Needs the disputes.read permission (Read Disputes).
Authorizations
A secret API key, made under Developers in the dashboard: Authorization: Bearer shoply_sk_...
Path Parameters
The store's ID. A key reaches the store it was made in: GET /key answers which.
Query Parameters
Part of the buyer's email, the order's ID or the provider's ID for the dispute.
Only these: open is the two that have not ended.
all, open, needs_response, under_review, won, lost, accepted, closed Only disputes with this payment method, by its ID.
"stripe"
Which page of the list. The first is 1.
How many a page holds.

