October 2026 (2026.10.1)

This release adds production orders, through a new outbound endpoint and a new webhook trigger. It also makes webhook filters, retries and task reporting more predictable.

New Features ✨

Production Orders

• GET /replenishment/production-orders returns the production orders submitted from Replenishment Scheduling or from Order Builder in production mode.
• The new ProductionOrderSubmit webhook trigger delivers the same orders as they are submitted. Enable it under Triggers in POST /webhook/settings.

Enhancements 🔨

Tasks

• GET /tasks, GET /tasks/{TaskId} and the task_status_update webhook now include UpdatedOn, the time a task held for review was approved or rejected.

Webhook Settings

• A webhook configuration's Authorization now reads back with only the configured method; one with none reads back as {}.
• Boolean fields accept quoted values ("true", "false") on every endpoint, as numbers already did.
• Filters on ExtendedData.<ApiLabel> now accept every operator, including >, <, >= and <=. Values are compared by the type of the underlying field: numbers numerically, text as exact text.

Bug Fixes 🐜

• PUT, PATCH and DELETE /webhook/settings/{configurationId} and GET /webhook/{webhookId}/payload answer 404 for an id that does not exist. They used to answer 400.
• On v1 webhooks, a failed delivery is now retried the full RetryHandling.Attempts times; it used to be retried once fewer.
• GET /webhook/history now numbers attempts from 1 on both v1 and v2 webhooks. On v2, a delivery that has used up its retries is no longer retried again after a restart.
• A cancelled task now reports the user who cancelled it in UpdatedBy.
• Custom extended data linked through a buyer or receiving location is now returned on GET /replenishment/work-orders, GET /replenishment/purchase-orders and GET /replenishment/transfer-orders; it was returned empty.
• Resending a webhook whose configuration has since been deleted now answers 400, saying so, instead of 500.