Resolve Unconfirmed Refund
POST/api/purple-dot/refunds/:refund/resolve
Closes a refund Purple Dot never confirmed (uncertain: true, listed in the refund preview's pending_refunds) with what the merchant found after checking the Purple Dot Merchant Portal. Runs under the same per-order lock as sending a refund, so it cannot race a retry or a late confirmation.
inventory:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
resolution: refundedrecords the refund as completed with the lines and shipping as sent: statussucceeded, a note on the sales order and a Refund row in the connection's Activity, the same as a confirmed refund. A later retry (byrefund_idor the same request) answers from this record and never re-sends.resolution: not_refundedsets statusnot_refunded: its units and shipping are released, so a new refund can be sent; it drops off the dashboard's Needs attention list, and retrying it byrefund_idis refused.
Both record who resolved it and the note in resolution and in Activity.
Body fields:
- resolution (string, required):
refundedornot_refunded. - note (string, optional, max 1000).
Response: the refund (same shape as Create Refund) with resolution = {outcome, user_id, user_name, note, resolved_at}; response_code is null for a refund resolved by hand.
Errors (422 with message, error_code, refund_id):
refund_not_pending: the refund is no longer unconfirmed (Purple Dot confirmed it meanwhile, it was already resolved, or Purple Dot rejected it). Nothing was changed.not_purple_dot: the order is no longer linked to a Purple Dot connection.purple_dot_error: a refund for the same order is being sent right now; wait, then try again.invalid_lines: the refund no longer exists.- Validation (422
errors):resolutionmissing or not one of the two values;notetoo long.
Authentication: Requires a Bearer token. Requires the sales_orders.update permission (the same as issuing a refund).
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden
Response Headers
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Content
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.