Resolve a dispute
Finalise a dispute with a validated resolution — the terminal ADVERTISER_RESPONDED → RESOLVED (or ESCALATED → RESOLVED) leg. When kind is SETTLEMENT_ADJUSTMENT, the route builds the settlement-application OVERRIDE that corrects the disputed attribution and appends it in the SAME atomic write as the dispute transition; the resolution’s settlementAdjustmentId carries the override id. The original application is located via the dispute’s evidenceBundle.settlementApplicationIds (or an explicit originalApplicationId when the bundle links more than one). Lookup failure is NON-FATAL: the resolve still succeeds and the response carries overrideApplied: false plus an overrideSkipped machine reason so the operator can re-run the adjustment by hand. Requires scope settlement:write.
Authorizations
API key sent as Authorization: Bearer <api-key>.
Path Parameters
Delivery dispute id (prefixed dispute:).
Body
CREDIT_ISSUED, MAKEGOOD_DELIVERED, SETTLEMENT_ADJUSTMENT, NO_CREDIT, OTHER Defaults to the key's developerId.
Required when kind is CREDIT_ISSUED.
Required when kind is MAKEGOOD_DELIVERED.
Required when kind is SETTLEMENT_ADJUSTMENT — map of partyRole → signed integer cents (negative reduces the party's amount). Must carry at least one finite integer.
Optional explicit linkage to the settlement application the adjustment corrects; disambiguates when the evidence bundle links more than one.