Receive Receipt

Marks an existing Aspire receipt as received. This action accepts the receipt identifier only and does not perform receipt-level edits. It cannot set or change invoice metadata, notes, extra costs or freight, receipt items, received date, or any other receipt field. If the user wants to record vendor invoice number or vendor invoice date around the same workflow, use approveReceipt because approveReceipt is the only post-create path for those two fields. For any other requested change to an existing receipt, explain that Aspire has no updateReceipt or patch action and the receipt must be recreated with the correct 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

Try this request

Request

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