Update CustomerPrepayment record
Changed onUpdate an existing CustomerPrepayment record with the provided data. Validates all required fields and business rules.
Side effects
- If an approval workflow matches this request, DualEntry can set record_status back to draft.
- If this record already has an active bank match, and an approval workflow holds the record, DualEntry returns those matches to draft.
Request
- Base URL: https://api.dualentry.com
- URL: https://api.dualentry.com/public/v2/customer-prepayments/{record_number}/
- Auth: none declared
Path parameters
The number attribute of the record.
Headers
Optional. A unique value (a UUID works well) identifying this operation. If the request is repeated with the same key, the original response is replayed instead of the operation running again, so a retry cannot create a duplicate record. Results are replayable for 48 hours. Reusing a key with a different request body returns 422.
Request body
Response
OK
Changes
- info
added the optional property
/////to the response with the status
- info
- info
added the optional property
//to the response with the status - info
added the optional property
//to the response with the status - info
added the optional property
//to the response with the status - info
added the optional property
//to the response with the status - info
added the optional property
//to the response with the status - info
added the optional property
//to the response with the status
- info