Create resend order
Resend
Create resend order
POST
Create resend order
Creates a resend order — bundles one or more received return inventory items into an outbound shipment to a customer address. Triggers asynchronous label generation; the label URL is delivered via webhook.
Prerequisites
- The target inventory items exist in your account. The
returnInventoryIdvalues come from thenewInventoryCreatedwebhook event — cache them on your side as parcels are logged. - All inventories in a single resend must be in the same warehouse.
- Each inventory’s current
handlingStatusCodemust be eligible to advance torsd(resend) per the handling state machine — typically items inohd(on-hold) status. - None of the items’ line items can have pending VAS requests.
- Each inventory must be physically in stock (not in-transit, not under another active workflow).
- Have your destination address ready.
Required fields
resendShipment— full shipment payload (destination address, contact, dimensions, weight, service type). Country codes are ISO3.shipmentServiceTypeinside the payload is a shipment service type (not a return service type) — fetch valid codes from Get available shipment service types for warehouse. Passing a return-service-type code here will fail validation.
returnInventoryIdList— non-emptyList<long>. Maximum size isResendConfig.groupResendMaxRmaCount(typically a single-digit cap; check via support if you need to bundle many items).
Side effects
- Each inventory’s
handlingCodeis set torsdand the matching status is applied. - The shipment is dispatched by the warehouse once the label is ready.
Related
- Get resend order details — only when a webhook event references a resend you haven’t cached.
- Cancel resend order — abort before the warehouse dispatches.
- Get all resend statuses — code-to-label mappings.
- Webhooks — resend-status-update event deliver lifecycle changes to your endpoint.
Authorizations
Your API key
Your API token — keep this private
Body
application/json
Response
Success
Created resend identifier