One dispute
A dispute belonging to another business answers 404, not 403 — a different answer for the two confirms it exists.
A dispute belonging to another business answers 404, not 403 — a different answer for the two confirms it exists.
Authorization
OAuth2PasswordBearer In: header
Path Parameters
uuidCookie Parameters
Response Body
application/json
application/json
curl -X GET "https://example.com/api/b/v1/disputes/497f6eca-6276-4993-bfeb-53cbbbba6f08"{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "charge_id": "cf8b747b-a752-4d0a-9a4d-7d19fc1769f3", "reason": "unauthorized", "description": "string", "status": "open", "evidence": {}, "resolution_notes": "string", "created_at": "2019-08-24T14:15:22Z", "updated_at": "2019-08-24T14:15:22Z", "resolved_at": "2019-08-24T14:15:22Z", "amount_minor": 0, "currency": "string", "charge_reference": "string"}Disputes against your charges GET
Every dispute raised against this business, newest first. Each row carries the disputed charge's amount and reference, so a list does not need a call per row to say what is at stake. `open_count` is computed over all of this business's disputes rather than the page: the page is filtered and paged, and a count taken from it would say "3 open" when it meant "3 open on this screen".
Submit evidence for a dispute POST
Add to what has already been submitted. Merged rather than replaced: a business that uploads a receipt and later a delivery note has provided two things, and a PUT-shaped endpoint would discard the first without saying so. 409 once the dispute is resolved or closed. Submitting into a decided case would record evidence nobody will read and imply it might still change the outcome.