The Update Order API changes an existing Draft order and re-runs the same pricing and tax cascade the Nue Line Editor runs internally. It is the write counterpart to Create Order, and the exact mirror of Update Quote.

Quote and Order share the same Line Editor, the same pricing engine, and the same tax cascade, so every operation, action name, payload shape, ordering rule, recalc mode, and error code is identical. Read Update Quote Overview for the full contract. This page covers the endpoint and the handful of things that differ on orders.

There is no separate preview endpoint. Preview is isCommit: false on the same call.

You do not send the order you want. You send an ordered list of actions naming what to do, each with its own payload. Fields you omit are untouched; lines you omit are untouched. A line is deleted only when you ask for it by id in a deleteLineItems action -- the server never infers a deletion from a shorter line list.

This is what separates the Update Order API from PATCH /api/objects/Order/{id}. The Objects API writes the field you send and recalculates nothing, leaving totals and tax stale. Partner payout is an exception: PATCH /api/objects/Order/{id} with partnerPayoutPercentage or partnerPayoutAmount re-prices the order, with the same validation as Update Order, while partner fields are not supported on PATCH /api/objects/OrderList and POST /api/objects/composite/*List, which return 400 wherever your API role can reach them. This API applies the change and re-runs pricing, roll-ups, and tax in the same transaction.

See Action-oriented, not payload-oriented on the Quote page for the full explanation.

The order is identified by the {orderId} path parameter. Do not put orderId in the body.

Identical to the Quote API:

Actions are re-ordered server-side into the canonical sequence -- header fields, deletes, price-tag actions, line updates, adds. updateHeaderFields may appear at most once, and each line may be targeted at most once; both violations return CONFLICTING_ACTIONS.

The sort is stable by stage: within a stage, actions keep the order you sent them. That is immaterial everywhere except the price-tag stage, where removePriceTags and replacePriceTags share a stage and their target line ids are not covered by the conflict check -- so two overlapping tag actions run in submitted order and the result depends on it. See Action ordering.

fieldValues keys are validated against the Nue object describe for Order (header actions) and OrderProduct (line actions). Use the Nue camelCase API names -- name, paymentTerm, billCycleDay, subscriptionTerm, quantity, discount, netSalesPrice, includedUnits, evergreen. Custom fields use their Salesforce API name (Region__c).

An unknown key fails at the proxy with 400 Invalid field for order: <name>. Salesforce field API names such as SubscriptionTerm__c are for the Apex global method, not for REST.

AUTO (default), PRICING_ONLY, TAX_ONLY, NONE -- case-sensitive, same semantics as on quotes. See Recalculation modes.

Pricing engine plugins run on the update exactly as they do on create -- but only when the request actually reaches the pricing pass. They do not run under recalc: NONE or TAX_ONLY, nor under AUTO when you only touched non-repricing fields. Preview runs them too. See Pricing engine plugins and recalc.

There is no reconfigure action -- you add, re-quantify, or delete the bundle's option lines. parentLineId points at the bundle line.

See Custom Fields.

Failures return 400 or 500 with { status, error, message, errorDetails[] }. Each errorDetails entry has an errorCode and a message. See Response on the Quote page.

The rules are identical to quotes, with OrderProduct field names in place of QuoteLineItem names.

Header fields never updatable -- FIELD_NOT_UPDATABLE: totalAmount, totalAmountWithoutTax, subtotal, listTotal, grandTotal, systemDiscount, systemDiscountAmount, totalCommittedAmount, sellerTotalAmount, tax, orderACV, orderTCV, todayARR, todayCMRR, id.

Deliberately updatable inputs: discount, discountAmount, totalPrice, partnerPayoutPercentage, partnerPayoutAmount.

Partner payout. Send one of the two partner fields; Nue derives the other. Sending both returns PARTNER_PAYOUT_MUTUALLY_EXCLUSIVE. Use the Nue names -- the Ruby__PartnerPayout*__c names return 400 Invalid field. Beyond the quote rules in Partner payout:

Change orders follow the change-quote rules: the header percentage applies to every change line, an amount converts to a percentage against the change total (summary line excluded), and a negative line's payout is the percentage x its total. The summary line's percentage is its payout divided by its own total. Set the payout here after the change order is created: POST /cpq/change-order and POST /cpq/change-order:preview ignore partner payout fields (the request succeeds and nothing is written). Under recalc: PRICING_ONLY, a change order keeps its stored tax and totalAmount = totalPrice + that tax.

Guarded separately: currencyIsoCode cannot change; the account cannot change; priceBookId cannot change once the order has priced lines (PRICEBOOK_CHANGE_NOT_ALLOWED).

Line fields that re-price: quantity, netSalesPrice, discount, discountAmount, subscriptionStartDate, subscriptionEndDate, subscriptionTerm, includedUnits, evergreen, plus line-direct Quantity Tier Attribute custom fields.

Line fields saved without re-pricing: billingPeriod, billingTiming, paymentTerm, billCycleDay, billCycleStartMonth, autoRenew, defaultRenewalTerm, description, cancellationDate.

Line fields never updatable: listPrice, listTotalPrice, unitPrice, netSellerPrice, subtotal, totalPrice, totalAmount, totalAmountWithoutTax, sellerTotalAmount, tax, systemDiscount, systemDiscountAmount, every delta* metric, actualQuantity, actualSubscriptionTerm, proratedQuantity, partnerPayoutPercentage, partnerPayoutAmount -- plus identity and relationship fields id, orderId, priceBookEntryId, productId, parentOrderProductId, productOptionId.

Line-type rules are the same: summary, split, ramp, and subscription-context lines are not editable; required and bundled children cannot be removed alone; removing a bundle root removes its whole descendant closure; change lines are removed only via their summary line.

An address or taxation-override change always triggers a tax recalculation when taxation is enabled, then rolls the header total up. recalc: TAX_ONLY is the cheap address-only path. The taxable-address override (five taxation* fields, activated by taxationCountry) and the taxation-customer identity resolve independently, Order first, then Account. See Addresses and taxation.

The order id is req.orderId, and fieldValues keys are Salesforce field API names (SubscriptionTerm__c), not Nue names. The response is { status, data, warnings, errors }. There is also an in-org apexrest surface at POST /services/apexrest/Ruby/updateOrder taking the same JSON body.

Full Apex documentation lives in the Nue Knowledge Center under Global Methods.