Skip to content
MothershipDevelopers

Webhook eventsRebills

Rebill created

Sent when a rebill is billed to your organization.

EVENTshipment.rebill.created
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:7a633610ed5e2d7a95c923679df505da3e6b1eb752e1c6e9436666a929e57568
X-Mothership-Delivery-Id:3f6c1a9e-8b2d-4c7a-9e15-2d8b7f4a6c01
{
: "shipment.rebill.created",
: {
: "MS123456",
: {
: "0c9a3f6e-2b7d-4e18-9a5c-7f1d2e4b8a63",
: "MSSR123456",
: "scheduled",
: "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 when a carrier's extra charges are billed to your organization. A new rebill is usually scheduled, and you have until rebill.disputableUntil to accept or dispute each line item before it is charged. Rebills explains the review.

Mothership sends rebill events only for rebills your organization is charged for, the same ones List rebills returns.

Subscribing

Add shipment.rebill.created 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 · 2 keys
  • shipmentIdstring

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

  • 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.created 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.status.updatedSent when a rebill's status changes.shipment.rebill.dispute.createdSent when a line item on a rebill is disputed.Receiving webhooksVerify the signature, answer within 30 seconds, and handle retries and duplicates.