Skip to main content

Outstanding Shipment Sync

Use this API to sync outstanding shipment quantities in bulk. Each row updates one retailer, optional shop, and offer combination.

At A Glance

PUT/v2/shipments/outstanding/sync-data
AreaDetail
Base URLhttps://api.mulltiply.org
Content typeapplication/json
Authenticationx-api-key request header
Request bodyArray of outstanding shipment records
Object shapeFlat object, no nested fields

Headers

Content-Type: application/json
x-api-key: YOUR_API_KEY

Request Body

Request body
[
{
"retailerSyncId": "RET-2001",
"shopSyncId": "00003",
"outstandingQuantity": 3,
"offerSyncId": "OFFER-1001"
}
]

Field Mapping

API fieldSource fieldRequiredDescription
retailerSyncIdretailerSyncIdYesRetailer identifier.
shopSyncIdshopSyncIdNoShop identifier. Can be null.
outstandingQuantityoutstandingQuantityYesOutstanding shipment quantity.
offerSyncIdofferSyncIdYesOffer identifier.

Processing Rules

  1. Send one object per outstanding shipment record.
  2. Pass retailerSyncId directly from the source.
  3. Pass shopSyncId directly when available, or null when not available.
  4. Pass outstandingQuantity directly from the source.
  5. Pass offerSyncId directly from the source.
  6. Treat each object independently during processing.

Final Payload Example

Final payload
[
{
"retailerSyncId": "RET-2001",
"shopSyncId": "SHOP-2001",
"outstandingQuantity": 3,
"offerSyncId": "OFFER-1001"
},
{
"retailerSyncId": "RET-2002",
"shopSyncId": null,
"outstandingQuantity": 5,
"offerSyncId": "OFFER-1002"
}
]

Source Data Checklist

Source columnSourceUsed for
retailerSyncIdSource APIRetailer identification
shopSyncIdSource APIShop identification
outstandingQuantitySource APIOutstanding quantity
offerSyncIdSource APIOffer identification

Implementation Checklist

  • Confirm every row has retailerSyncId.
  • Confirm every row has offerSyncId.
  • Confirm outstandingQuantity is numeric.
  • Send shopSyncId as null when no shop is available.
  • Send a JSON array for both single and bulk updates.