Update a receipt
PUT/panel/receipts/:receipt
Updates the receipt identified by its UUID.
Omitted fields are reset: tax, receipt_url and description are always written from the request, so leaving any of them out clears the stored value. Send the current values to keep them.
workspace_uuid is accepted but ignored — a receipt cannot be moved to another workspace through this endpoint.
quantity is reset to 1 on every update.
Request
Responses
- 200
- 401
- 403
- 404
- 422
success reflects whether the receipt row was written, so it can be false when the submitted values match the stored ones.
The bearer token is missing, malformed, unknown, or expired.
The token is valid, but the user it belongs to may not perform this action:
- they are not a member of the
{workspace}in the path; or - their workspace role is too low for this endpoint (write routes require Admin or Member); or
- for
/panelendpoints, they are not a platform administrator.
The host application that Mixpost is installed into can also deny access to Mixpost as a whole, which produces the same response.
The requested record does not exist. The message names the missing record — for example Post not found., Tag not found., Media not found., Account not found. or User not found.
The request body failed validation.