Skip to content
COMMERCE SERVICES
/
Order Service
/
/
Tracking

Documentation OrderService (1.1)

The Orders namespace has Entities and Operations used for orders and other related Entities such as DeliveryNotes and Invoices. This namespace has nothing to do with the Checkout process where orders are created, but is more related to order history shown on pages like MyPage and such. The Order history in Storm is mostly a snapshot view of the orders as they looked when they got created in Storm, unless process integrations exists where DeliveryNotes and Invoices are passed to Storm.

Download OpenAPI description
openapi.json
openapi.yaml
Languages
Servers
https://customer-slug.api-se.norce.tech/commerce/order/1.1/

Schemas

Schemas

OrderPagedList2

ItemCountinteger(int32)

The total number of orders. Can be used to manage paging. Use PageSize to calculate number of pages.

ItemsArray of objects(OrderListItem)(OrderListItem)

Current list of orders for the current page if paging is used. Otherwise all orders will be in the list.

{
  "ItemCount": 0,
  "Items": [
    { … }
  ]
}

Tracking

Idinteger or null(int32)
FreightForwarderstring

MaxLength: 50.

TrackingCodestring

MaxLength: 50.

{
  "Id": 0,
  "FreightForwarder": "string",
  "TrackingCode": "string"
}

IdNameDescription

Idinteger(int32)

The internal Id of the Entity.

Namestring

The Name of the Entity. MaxLength: 50.

Descriptionstring

The Description of the Entity. MaxLength: 500.

ImageKeystring or null(guid)

A unique id for the image at our image server. Url for images are formed like http://[client specific CDN]/{ImageKey}. Preset, height and width can be sent as parameters.

Codestring

The Code of the Entity. MaxLength: 50.

{
  "Id": 0,
  "Name": "string",
  "Description": "string",
  "ImageKey": "string",
  "Code": "string"
}

DeliveryNotes

Operations

InfoTypes

Operations

Invoices

Operations

Orders

Operations