Update Expense Rule

Updates an existing expense rule in Expensify.

PUT

Query

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

string

Comma-separated response fields to include.

Body

Arguments

stringrequired

The policy to update the rule on.

stringrequired

The policy member who should receive the expense rule.

stringrequired

The expense rule ID to update.

stringrequired

JSON object containing supported rule actions, for example {"tag":"Tag Name"}.

Try this request

Request

curl --request PUT \
  --url "https://connect.mindcloud.co/v1/universal/expensify/latest/actions/update-expense-rule" \
  --header "Authorization: Bearer $MINDCLOUD_API_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{
  "connectionId": "$CONNECTION_ID",
  "policyId": "BE9009315B111E6A",
  "employeeEmail": "[email protected]",
  "ruleId": "999999",
  "actionsJson": {
    "defaultBillable": false
  }
}'

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