Update Return Cause

Updates a return cause in Webshipper.

PUT

Query

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

string

Comma-separated response fields to include.

Body

Arguments

string

Repeat the ID value for the JSON:API request body.

string

Updated return cause description.

string

The return cause ID.

string

Whether refund methods should be limited.

string

Updated return cause name.

string

Whether a comment is required for this return cause.

string

Whether a support image is required.

stringrequired

Use the default value `return_causes`.

Try this request

Request

curl --request PUT \
  --url "https://connect.mindcloud.co/v1/universal/webshipper/0.0.6/actions/update-return-cause" \
  --header "Authorization: Bearer $MINDCLOUD_API_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{
  "connectionId": "$CONNECTION_ID",
  "data.type": "return_causes"
}'

{
  "success": true,
  "data": [
    {
      "description": "string",
      "id": "string",
      "limit_refund_methods": true,
      "name": "Ava Chen",
      "require_comment": true,
      "support_image_required": true,
      "type": "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.