List Fulfillments

Retrieve existing Fulfillments.

POST

Body

Arguments

string

(optional) A Rithum generated unique identifier for a specific Fulfillment.

string

(optional) Use a custom filter. (oData). Examples:

OrderID eq 20008076
CreatedDateUtc ge 2016-03-02 and CreatedDateUtc lt 2016-03-03

string

(optional) Expand a specific sublist (i.e. Items on this Fulfillment.)

Field selectionChoose which fields should be included in the response. Learn more

string

Comma-separated response fields to include.

Try this request

Request

curl --request POST \
  --url "https://connect.mindcloud.co/v2/universal/apps/rithumForBrands/actions/list-fulfillments/run" \
  --header "Authorization: Bearer $MINDCLOUD_API_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{
  "arguments": {}
}'

{
  "success": true,
  "data": [
    {
      "channelReturnLabelFormat": {},
      "createdDateUtc": "string",
      "deliveryStatus": "string",
      "distributionCenterID": 1,
      "earliestDeliveryDateUtc": {},
      "earliestShipDateUtc": {},
      "estimatedDeliveryDateUtc": {},
      "estimatedShipDateUtc": {},
      "externalFulfillmentCenterCode": {},
      "externalFulfillmentNumber": {},
      "externalFulfillmentReferenceNumber": {},
      "externalFulfillmentStatus": "string",
      "hasChannelPackingSlip": true,
      "hasChannelReturnLabel": true,
      "hasReturnLabel": true,
      "hasShippingLabel": true,
      "id": 1,
      "insuranceCost": 1,
      "items[]": {
        "distributionCenterCalculatedItemUnitCost": {},
        "distributionCenterCalculatedShippingCost": {},
        "distributionCenterItemUnitCost": {},
        "distributionCenterShippingCost": {},
        "fulfillmentID": 1,
        "id": 1,
        "marketplaceShippingStatus": "string",
        "orderID": 1,
        "orderItemID": 1,
        "productID": 1,
        "profileID": 1,
        "quantity": 1,
        "referenceProductID": {},
        "referenceSku": {},
        "sellerFulfillmentItemID": {},
        "sku": "string",
        "warehouseLocation": {}
      },
      "labelFormat": {},
      "orderID": 1,
      "profileID": 1,
      "returnLabelFormat": {},
      "returnTrackingNumber": {},
      "sellerFulfillmentID": {},
      "serialShippingContainerCode": {},
      "shippedDateUtc": {},
      "shippingCarrier": "string",
      "shippingClass": "string",
      "shippingCost": 1,
      "shippingLabelRequestID": {},
      "stagingLocation": {},
      "taxCost": 1,
      "trackingNumber": {},
      "trackingUrl": {},
      "type": "string",
      "updatedDateUtc": "string"
    }
  ],
  "meta": {}
}

Every app you connect,one REST pattern

Call any app with one REST pattern. MindCloud handles each provider's auth, request shape, and responses for you.

Learn what the Universal API is

One REST patternUse the same request structure across apps like Slack, HubSpot, Salesforce, and thousands more.

Managed connectionsSend a MindCloud connection ID instead of handling provider tokens, refresh logic, and credential storage yourself.

Action-level docsEach action page shows the exact endpoint, required arguments, optional controls, and response behavior for that app version.