under_review.
Status model
The order schema can return:under_review to approved or rejected. Other lifecycle transitions are server-managed or performed outside this operation.
HR review swimlane
The public contract confirms that approval sends corresponding notifications, but it does not enumerate recipients or delivery channels. Do not build customer logic that depends on an undocumented recipient list.Retrieve work
Review current state
Immediately before a decision, callGET /orders/{id} and verify:
- status is still
under_review - the employee matches the expected record and the request uses the intended tenant context
- product model, manufacturer, article group, VAT, gross and net amounts, service amounts, and accessory classification match the review
- contract fields are acceptable
- required attachments are available
vatRate, grossAmount, netAmount, grossService, and netService are decimal strings. Preserve their precision and use an exact decimal type for calculations. model, manufacturerName, articleGroupName, service, grossService, and netService can be null as defined by the schema.Order responses no longer contain
tenant or divisionId. HR review information is returned in hrHistory, and decisionBy is a nullable user ID rather than the previous actor-category value.Validate and apply
dryRun=true.
Concurrency and finality
Conflict handling
Download order documents
Use the attachment ID returned by an order:Content-Type before treating the response as a file. Retry transient download failures with bounded backoff.