Skip to content
MothershipDevelopers

Webhook eventsRebills

Rebill dispute resolved

Sent when a rebill dispute is approved, charged, withdrawn or closed.

EVENTshipment.rebill.dispute.resolved
POST to your endpointSigned with HMAC-SHA256Retried for up to 4 daysPermission to read rebills
RequestPOSThttps://your-server.example.com/webhooks/mothership
Content-Type:application/json
X-Mothership-Signature:a519a10e050062ac56bbb4eb69719acc98d15bb108c15d1d925088151bfc713f
X-Mothership-Delivery-Id:3f6c1a9e-8b2d-4c7a-9e15-2d8b7f4a6c01
{
: "shipment.rebill.dispute.resolved",
: {
: "MS123456",
: {
: "e3b4c2d1-7a6f-4b9e-8c5d-1f2a3b4c5d6e",
: "5b0e7c1a-9f4d-4c8e-a2b6-3d1f8e7a6c40",
: "resolved-approved",
: "Wasn't performed",
: null,
: "2026-10-09T18:22:10.000Z"
},
: {
: "0c9a3f6e-2b7d-4e18-9a5c-7f1d2e4b8a63",
: "MSSR123456",
: "disputed",
: "7012345678",
: 8500,
: 1500,
: 10000,
: "usd",
: "2026-10-22T15:04:05.000Z",
: null,
: [
4 keys
]
}
},
: "2026-10-08T15:04:05.000Z",
: 1,
: 16
}

Hover a key to see what it means. Click it to jump to the field.

Sent once when a dispute reaches its outcome. dispute.status is the outcome: approved, charged, withdrawn or closed.

Subscribing

Add shipment.rebill.dispute.resolved to a configuration's subscribedEvents with Create a webhook configuration or in the dashboard. The token needs permission to read rebills. Without it, the request answers 403 MISSING_PERMISSION, and opening or resending these deliveries in the dashboard is refused too. Such a token can still remove the event from a configuration.

Event data

data · 3 keys
  • shipmentIdstring

    The shipment's reference number, such as MS123456. Pass it to Get shipment details.

  • disputeobject

    The dispute as it is when Mothership sends the event.

  • rebillobject

    The rebill as it is when Mothership sends the event, named as Retrieve a rebill names it. Call that with rebill.id for what each charge means.

Envelope

Same on every event
  • eventTypestring

    The event. Always shipment.rebill.dispute.resolved here. Route on it, and answer 2xx to types you don't handle.

  • sentAtstring

    When Mothership queued the event to send, as an ISO 8601 string in UTC. Every retry and resend carries the same value, so it does not say when this attempt went out.

  • deliveryAttemptinteger

    Which send of this event this is, starting at 1. Resends from the dashboard count too.

  • pendingRetriesinteger

    How many automatic attempts are left if this one fails. 0 on the last one.

Related

shipment.rebill.dispute.status.updatedSent when a rebill dispute's status changes.shipment.rebill.finalizedSent when a rebill's review is over and it will be charged.Receiving webhooksVerify the signature, answer within 30 seconds, and handle retries and duplicates.