Docs

Split Orders

Use this API to confirm an order split. Note that ​​supported split levels vary by region​​: - Some regions support ​​item-level splits​​ (splitting individual units of the same SKU). - Others only support ​​all-units splits​​ (splitting different SKUs into separate packages). Here are two examples of supported splits: - ​​Case 1: all-units split​​, applicable for orders in BR, SEA, MX (local sellers) Split a buyer order of SKU A of quantity 2 and SKU B of quantity 1 into two separate packages: - ​​Package 1​​: all units of SKU A ​​ - Package 2​​: all units of SKU B - ​​Case 2: item-level split​​, applicable for orders in EU, JP, MX (global sellers), UK, US Split the same order contents into three individual packages: - ​​Package 1​​: 1 unit of SKU A ​ - ​Package 2​​: 1 unit of SKU A ​​ - Package 3​​: 1 unit of SKU B

POST

Query

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

Comma-separated response fields to include.

Body

Arguments
string
string

A unique identifier designated by the developer. This identifier will represent a group of items that will be split into a new package. Once split is confirmed, the platform will be assigned a new package ID for this group of items. For example, if you input 123 as request, the response will return 123 as your unique identification. The seller uses this field to label each group of items that have been split, and the platform will assign new package IDs to them.

object

Input list of splittable groups.

string
array

The order line item IDs that need to be split into this group.

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.