COMMERCE SERVICES

Shopping Service

NameValue

Norce Commerce Shopping v1.1 service (1.1)

Entities and methods to handle baskets and payments. The Shopping service is used to create and manage baskets, and prepare them for the checkout process. Commonly the checkout process is handled by the Norce Checkout API, only the legacy checkout process is handled here. For product or pricing data, use the Product service. For order history, use the Order service. To change or manage promotions use the Management API.

Download OpenAPI description

openapi-v1.json

openapi-v1.yaml

Servers

Playground

https://{slug}.api-se.playground.norce.tech/commerce/

Stage

https://{slug}.api-se.stage.norce.tech/commerce/

Production

https://{slug}.api-se.norce.tech/commerce/

Basket

Contains endpoints for manage baskets and their lifecycle, see more information here.

Operations

Checkout

Contains endpoints for initialized the checkout process, read more about it here. There is also the old legacy purchase endpoints, still used by older solutions and Non-PSP purchases.

Operations

DeliveryMethods

Contains endpoints for viewing metadata about configured delivery methods, when using Norces internal shipping logic.

Operations

InfoTypes

Contains endpoints for viewing metadata for extended fields on the basket and basketitems.

Operations

OnHand

Contains endpoints for looking up availability on baskets.

Operations

OrderRequest

Contains endpoints for viewing orders snapshots.

Operations

Payments

Contains endpoints for legacy purchases, still used by older solutions and Non-PSP purchases.

Operations

Promotions

Contains endpoints for viewing more promotion information.

Operations

Schemas

InsertItemsPostPurchaseData

Used as input to InsertItemsPostPurchase since WCF cannot take more than one complex type at once as parameter.

ItemsToAddArray of objects or null(BasketItem)

The items to add to the purchase. The items to insert must have its PartNo, Quantity and PriceListId set. ParentLineNo, Name, Comment, ReferId and ReferUrl can be used if other values than the default are wanted. All other properties will be populated from the system.

PaymentParametersArray of objects or null(NameValue)

Roundtrip of the parameters received in the original payment response.

{
  "ItemsToAdd": [
    { … }
  ],
  "PaymentParameters": [
    { … }
  ]
}

NameValue

An Entity used where Name and Value is needed. Mostly used for lookup data.

Namestring or null

The Name of the Entity.

Valuestring or null

The Value of the Entity.

{
  "Name": "string",
  "Value": "string"
}

OnHand

Information about OnHand for a given SKU. There are generally three different types of OnHand in Norce. One for the Web, one for the chosen supplier and one for any specified Store.

Valuenumber or null(decimal)

The aggregated value from all warehouses and locations in the current context (Web, Supplier or Store).

IncomingValuenumber or null(decimal)

The incoming quantity on the next delivery.

NextDeliveryDatestring or null(date-time)

The next delivery data from supplier to client warehouse.

LeadtimeDayCountinteger or null(int32)

The number of days it takes to ship from the supplier.

LastCheckedstring or null(date-time)

When onHand info was last checked. Null if never.

IsActiveboolean or null

Indicate if the product is stocked in a store.

IsReturnableboolean or null

Indicate if the product is returnable in a store.

InfoArray of objects or null(IdValue)

List of IdValues for the OnHand data for this sku warehouse location combination. This will always be null unless fetched with any of the ProductOnHand methods.

{
  "Value": 0,
  "IncomingValue": 0,
  "NextDeliveryDate": "2019-08-24T14:15:22Z",
  "LeadtimeDayCount": 0,
  "LastChecked": "2019-08-24T14:15:22Z",
  "IsActive": true,
  "IsReturnable": true,
  "Info": [
    { … }
  ]
}