Skip to content
platform
EN PT

API reference · Orders · Marketplace Management

Send Item Tracking - Marketplace

Method
POST
Route
/partnerOrders/store/:id/complementaryInfo
Base URL
https://ws.autorei.net
Path parameters
:id
Token
Requires Bearer token
Test in Postman

Opens this request in the public API documentation, the official source of the reference.

Description

Allows the originating store to report, item by item, the status of each product in an order that originated in it.

The body and the response are identical to those of the store route; what changes is the scope of the sender.

Path Parameters

Parameter Type Required Description
id integer Yes Id of the partner order (partnerOrderId).

Request Body (JSON)

Field Type Required Description
skus array Yes The tracking items. From 1 to 250 per request.
skus[].partnerPartCode string Yes Your part code for the product, the same one you registered in inventory.
skus[].situation string Yes Item status. Free text — the platform does not validate it against a list.
skus[].quantity integer Yes Quantity in that status. Integer greater than zero.

Business rules

The submission reaches only the parts it contains

The scope of the submission is the item, not the order: each request replaces the tracking of the parts it cites and leaves the others intact. You can send one product at a time, without resending the whole order.

Resending an item exactly equal to what is already stored does not recreate the record: it is preserved as it is.

The same product in more than one status

partnerPartCode can repeat in the same submission, once per status — this is how you report three units shipped and two in preparation of the same product. The quantities add up; the records do not compete with each other.

The sum does not exceed the item quantity in the order

For the same product, the sum of the reported quantities cannot exceed the quantity of that item in the order. If it does, the request is rejected and nothing is stored.

The product must be in the order

The partnerPartCode is resolved against the lines of that order. A code that matches no line, or that matches more than one, rejects the request — and the response says which code caused the rejection.

Response · 200

The echo of what you sent, with the verdict for each item. For the set stored in the order, use Get Item Tracking.

Field Description
orderId Customer order id, derived from the order in the path.
partnerOrderId Partner order id, the same as in the path.
skus[].partnerPartCode The code you sent.
skus[].quantity · skus[].situation Quantity and status reported.
skus[].status valid on the accepted item · invalid on the item that caused the rejection.

When the rejection is item by item

A rejection by business rule responds 422 with the same structure as success, plus status and message at the top: the items that caused the rejection come back with status: "invalid" and the others with valid, and message gathers the reasons, one per line. Nothing is stored — the rejection applies to the entire request. This way you locate the problem item without matching the message to its position in the array.

Errors

Code When
400 The body is not valid JSON. The detail comes in error.
422 skus missing, empty or with more than 250 items; item without partnerPartCode, without situation or with a quantity that is not an integer greater than zero; code that is not in the order or that appears in more than one line; sum above the item quantity. The body carries the reason in message and marks the rejected items.
404 The order does not exist or is not within your scope.
401 Token missing, malformed or expired.

Example request

curl --request POST 'https://ws.autorei.net/partnerOrders/store/:id/complementaryInfo' \
  --header 'Authorization: Bearer {{access_token}}' \
  --header 'Content-Type: application/json' \
  --data '{
  "skus": [
    {
      "partnerPartCode": "SKU-A-001",
      "situation": "enviado",
      "quantity": 2
    },
    {
      "partnerPartCode": "SKU-A-001",
      "situation": "preparando",
      "quantity": 1
    }
  ]
}'

Example responses

200Success — product in two statuses

{
  "orderId": 900100,
  "partnerOrderId": 900201,
  "skus": [
    {
      "partnerPartCode": "SKU-A-001",
      "quantity": 2,
      "situation": "enviado",
      "status": "valid"
    },
    {
      "partnerPartCode": "SKU-A-001",
      "quantity": 1,
      "situation": "preparando",
      "status": "valid"
    }
  ]
}

422Rejected — code that is not in the order

{
  "status": "UNPROCESSABLE_ENTITY",
  "message": "partnerPartCode não encontrado nas linhas do pedido: SKU-Z-999",
  "orderId": 900100,
  "partnerOrderId": 900201,
  "skus": [
    {
      "partnerPartCode": "SKU-A-001",
      "quantity": 2,
      "situation": "enviado",
      "status": "valid"
    },
    {
      "partnerPartCode": "SKU-Z-999",
      "quantity": 1,
      "situation": "enviado",
      "status": "invalid"
    }
  ]
}

Used in

Related endpoints

← See the group: Orders

Generated from the public API collection, published on 2026-09-04: api-docs.cws.digital.