Add Order Note


This documentation is for translated APIs and intended only for some implementations who have upgraded from a previous version of Order Management. Verify whether your implementation uses translated APIs before making this call, as you will experience errors if your tenant is not configured to use these. If your implementation is not configured to do so, then refer to the standard API documentation instead.

The Order Note API allows any user to add notes to orders and shipments, and mark them as publicly or privately visible.

Note that the request body and parameter schemas outlined in this guide are the exact same as in the previous version of OMS, as the Unified Commerce platform supports backwards compatibility for this API. The only change to this request is the format of the base endpoint, as shown in the below table. Remember to provide the x-vol-tenant key for authentication in the headers.

Production URLhttps://{tenantId}{orderID}
Sandbox URLhttps://{tenantId}{orderID}
Supported FormatsJSON


The example will add a note with the following properties to an order:

  • Public note on Order 44444
  • Written by user 012210

Required Parameters

Assigning an order requires:

userIDintegerA unique identifier for the user. The minimum value is “1”.
notestringThe body of the order note. The maximum length is 1000.
publicbooleanWhether the note is publicly viewable. The default is “true”.

Optional Parameters

There are several optional parameters that can add more details and ID associations to the note:

noteIDintegerA unique identifier for the order note.
noteTimestringThe date-time at which the note was created. Note that this ID is read-only – it is automatically assigned by OMS, so do not attempt to set this parameter.
orderIDintegerA unique identifier for the order. The minimum value is “1”.
externalOrderIDstringA client-generated unique identifier for the order. The minimum length is 1 and the maximum length is 100.
shipmentIDintegerA unique identifier for the shipment. The minimum value is “1”.
userNamestringThe user’s name. This parameter is also read-only, so do not attempt to set this parameter. Use the required userID instead.

The Full Request

The order that this note is being applied to should be specified in the URL endpoint.


The body contains all the information about the note itself.

 "note":"Here is another note.",

The returned response provides information about the note that was created, including the note text, user ID, order ID, and a new Order Note ID when applicable.