Update carrier tracking information for a specific order

If the carrier is not registered, the complete tracking url can be provided.

PUT

Query

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

string

Comma-separated response fields to include.

Body

Arguments

string

The code of a carrier. This information is mandatory for a registered carrier.

string

The name of a carrier. This information is mandatory for an unregistered carrier.

string

Carrier standard code

string

The tracking url of a carrier. This information is unused for registered carriers (because computed automatically). This information is optional for unregistered carriers.

string

Use this parameter when your user has access to several shops. If not specified, the shop_id from your default shop will be used.

string

The carrier tracking number. This information is mandatory for a registered carrier with a URL requiring a tracking number.

Try this request

Request

curl --request PUT \
  --url "https://connect.mindcloud.co/v1/universal/mirakl/0.0.11/actions/update-carrier-tracking-information-for-a-specific-order" \
  --header "Authorization: Bearer $MINDCLOUD_API_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{
  "connectionId": "$CONNECTION_ID"
}'

{
  "success": true,
  "data": [],
  "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.