Approve Receipt

Approves an existing Aspire receipt and can optionally receive it at the same time. This is the only post-create update path for a receipt. At approve time, the only receipt fields that can be added or changed are the vendor invoice number and vendor invoice date. No other receipt field can be edited through this action, including notes, extra costs or freight, receipt items, received date, vendor, branch, or work ticket. If the user asks to change a non-invoice-metadata field on an existing receipt, surface that limitation upfront and offer the available path of recreating the receipt with the corrected values.

POST

Query

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

string

Comma-separated response fields to include.

Body

Arguments

number

boolean

string

Try this request

Request

curl --request POST \
  --url "https://connect.mindcloud.co/v1/universal/aspire/0.1.470/actions/approve-receipt" \
  --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.