Approve or reject an order
Approves or rejects an order that is under HR review. Approval applies the documented contract date defaults and sends the corresponding notifications. With dryRun=true, the API returns the projected order without applying the decision or sending notifications.
At a glance
Operational behavior
Approves or rejects an order that is under HR review. Approval applies the documented contract date defaults and sends the corresponding notifications. WithdryRun=true, the API returns the projected order without applying the decision or sending notifications.
- Only an order in under_review is eligible for this public decision operation.
- A final decision cannot be overwritten through this endpoint.
- After timeout, re-read the order before any retry.
Common errors
Before implementation
- Generate and log a new
X-Request-IDfor the attempt. - Handle every documented response status.
- Do not log
X-API-Keyor unnecessary personal data. - Reconcile current resource state before replaying an ambiguous write.
Related integration guidance
Authorizations
JobHandy integration API key. Send the credential in the X-API-Key header. Treat the key as a secret and use it only from trusted server-side environments.
Headers
Narrows the operation to one tenant in the API key's scope. Any referenced or target resource must be accessible through that tenant. In interactive clients, use the {{tenantId}} variable when a tenant must be selected. Keep the header disabled when tenant selection is not required.
^[0-9a-fA-F]{24}$Optional request identifier. If supplied, it must be a UUID v4 or v7 and is returned unchanged in every response. If omitted, the API generates one. Invalid values return 400 INVALID_REQUEST_ID. If your client uses a {{requestId}} variable, refresh it with a new UUID version 4 or 7 for every HTTP request attempt. Keep the header disabled to let the API generate the request identifier.
^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[47][0-9a-fA-F]{3}-[89aAbB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}$Path Parameters
Order ID.
^[0-9a-fA-F]{24}$"69eb125feddfff1d13676751"
Query Parameters
When true, the API validates the request without applying the change. The operation's responses specify the returned representation. When omitted, the server uses false.
true
Body
The JSON request body must not exceed 5,242,880 bytes.
Approval or rejection to record for an order under HR review.
Target decision. Values are case-sensitive.
approved, rejected 1Response
Returns the decided order, or the projected order when dryRun=true.
Order details.
Unique order identifier.
^[0-9a-fA-F]{24}$"69eb125feddfff1d13676751"
Current order lifecycle status. Values are case-sensitive.
under_review, rejected, approved, active, archived, withdrawn 1"approved"
Identifier of the employee who placed or owns the order.
^[0-9a-fA-F]{24}$"68a000000000000000000001"
Human-readable numeric order number.
110495
UTC timestamp at which the order was created.
1Z$"2026-07-01T10:00:00.000Z"
UTC timestamp of the latest order update.
1Z$"2026-07-02T12:15:00.000Z"
Products and accessories included in the order.
Delivery address for the order, or null when no delivery address is available.
HR review request and decision history.
Contract duration in whole months, or null when not determined.
124
UTC contract start date, or null when not determined.
1Z$"2026-08-01T00:00:00.000Z"
UTC contract end date, or null when not determined.
1Z$"2028-07-31T23:59:59.999Z"
Order contract documents available through the order attachment download endpoint.
