Skip to main content
TroopyDocs
Open Troopy
Troopy

API reference / Disputes

Let a dispute go

Says that the business does not answer this dispute. Troopy then sends nothing for it, with or without a grant. The cardholder keeps the money when the deadline of the provider passes. Send undo true to take the decision back while the provider takes an answer. Owners and admins.

post/api/v1/disputes/{id}/let-go

Authorization

HeaderAuthorization: Bearer <API key>
Or the headerX-API-Key: <API key>
API keyMake one in Troopy under Settings > API keys. It acts as you, in its workspace.

Other ways to call it

CLItroopy disputes let-go
MCP toolNone. Call it over REST or with the CLI.
Rate limit20 calls in 60 seconds, for each key
RetriesSend an Idempotency-Key header. A retry with the same key gets the first answer back, and the operation runs one time.

Path parameters

id*string

The id of the dispute in Troopy, or its id at its payment provider, like du_1MtJUT2eZvKYlo2C in Stripe

At least 1 characters · At most 80 characters

Body

application/json
undoboolean

Take the decision back: Troopy prepares the evidence again

Default false

Response

200 · application/json
data*object
18 properties
id*string

A 24-character id

provider*enum<string>

The payment provider of the disputed payment. stripe: Troopy sends the evidence. dodopayments: a person uploads the evidence in the dashboard of Dodo Payments. paddle: Paddle answers by itself, and takes no evidence

stripedodopaymentspaddle

providerId*string

The id of the dispute at its provider. For Paddle, the id of the disputed transaction

live*boolean

false: a dispute of the test mode of the provider

amount*number

The disputed amount, in the units of its currency

currency*string
reason*string

The reason, in the words of Stripe: fraudulent, subscription_canceled or general, for example

status*string

The status, in the words of Stripe for each provider: needs_response, under_review, won, lost, prevented, or one of the warning_ statuses of an inquiry

customer*object
3 properties
id*string | null
email*string | null
name*string | null
filedAt*string

ISO 8601 date and time

dueBy*string | null

When the provider stops taking an answer

stage*enum<string>

Where Troopy is with it. preparing: it collects the evidence. waiting: the evidence waits for a person. submitting: it goes now. unknown: nobody knows if it went, and Troopy reads the dispute again. submitted: it went. let_go: a person decided not to answer. none: the provider takes no answer

preparingwaitingsubmittingunknownsubmittedlet_gonone

why*string | null

Why it waits for a person, or what went wrong

usage*enum<string>

The usage that the backend of the business sends. wanted: Troopy waits for it

nonewantedreceived

submittedAt*string | null
submittedBy*object | null

Who submitted the evidence, or said that it went. Under a grant: the person who granted it

3 properties
type*enum<string>

personagentapi

id*string
name*string
auto*boolean

Whether the evidence went under a grant, without a person

url*string

The dispute, or its payment, in the dashboard of its provider

Errors

400 invalid_inputFix the field named in detail. Each operation's schema is in /api/v1/openapi.json.
401 unauthorizedSend an API key as `Authorization: Bearer tr_live_...`. Create one in Troopy under Settings.
403 forbiddenThe key lacks a scope this operation needs, or its owner lacks the role. detail says which; create a key with the scope, or ask an organization owner or admin.
404 not_foundCheck the path and any id in it. Every operation is listed in /api/v1/openapi.json.
409 conflictThis Idempotency-Key was used for a different request, or that request is still running. Use a new key for a new request.
429 rate_limitedWait the number of seconds in Retry-After, then retry.