Process cart workflow test from a posted cart or order (Dry run of workflow).
Request
- Base URL: https://api.omnium.no (the document declares no server; this is the origin it was published from)
- URL: https://api.omnium.no/api/Orders/processExternalCartWorkflowTest/{status}
- Auth: API key in header Authorization
Path parameters
Request body
Cart unique ID
Expiration date of cart. If passed, the cart should not be visible to customer.
Should the cart be read only?
Should the order/cart be read only for the customer?
Should promotion prices be ignored when product is added to cart?
Customer groups (for discount calculation)
Should be used when order needs a special status when created from cart
In most cases, this property will be identical to the Id property. However, if you have orders from multiple sources (multiple e-commerce sites, pos systems or other sales channels), and the order numbers from the sources could overlap, you could set the Id to a unique value and the order number to the user friendly number.
The ID of the customer that has placed the order. Typically this is set to the customers phone number or email address, but it could be set to anything. A customer with the matching ID does not have to exist in the system before the order is placed. If there are no overlapping IDs, but you still have multiple sources of IDs, consider using ExternalIds instead.
In most cases, the customer number could be set to the same value as the CustomerId. However, in some edge cases the customers could get imported from multiple systems with the same ID range. In that case, you should set the user friendly number to the CustomerNumber and an unique ID for the CustomerId.
If Customer is member of customer club, set Customer ID as member ID.
Currency of the order. e.g. "USD","NOK"
Full name of customer
Customer phone number with prefix. e.g. +4740000000
Customer e-mail
B2B or B2C (Business customer or private customer)
Market ID e.g. "US", "NOR", "SWE". This must match the value of the market(s) defined in Omnium.
(OBSOLETE: Use property on OrderForm instead) Shipping discount amount
Total shipping cost
The current order status. This must match a status defined in the order settings in Omnium. Typical values are "New", "InProgress", "Cancelled" or "Completed".
CALCULATED: The remaining payment amount if the difference between the authorized amount and total amount
Id of seller of the order - typically set to the e-mail of the user in Omnium, but could be set to any ID.
Name of the seller of the order
Name of sales channel
CALCULATED: Order completed date
CALCULATED: Order last modified date
CALCULATED: Modified by
The creation date of the order
The received date of the order
Order follow-up date
CALCULATED: Customer deadline for picking up order
CALCULATED: Employee deadline for picking order
Delivery date requested by customer
Date when order should be moved to next status. (Updated by UpdateOrderStatusScheduledTask)
Calculated: When the order was set to ready for pickup. The property can be set by workflow step with name: Set ready for pickup date
Status order should be moved to. (Updated by UpdateOrderStatusScheduledTask)
OBSOLETE: Use orderForm.payments instead.
Order type e.g. "Online", "Pos". The order type must match a order type defined in the Omnium order settings
The allocation profile Omnium's allocation engine should rank plans under for this order, for example FewestShipments or Closest. Empty means the profile configured for the market.
The store Id identifies the store that sells the orders. Should match an ID of an existing store. A store would typically be the front end e-commerce solution, a physical store or other sales channels.
The origin of the order should identify where the order was created. Typical values are "OMS", "ERP", "WEB" or "POS".
Calculated: Total cost of the order. The cost price
Calculated: OrderForm total - returnForms total
Calculated: OrderForm total excl tax - returnForms total excl tax
Reference provided by customer.
Customer contact person
Customer requisition provided by customer
If true, Omnium's notifications will not be triggered for the order
List of related order IDs
Session code used for referencing a web session
A unique secret key for the order. Can be used for secure order lookups.
List of replacement order IDs for this order
Subscription ID - used if order is part of a subscription. The Id should match an existing subscription in Omnium
Project IDs - used if order is part of projects
Order tags (Used by notification filters, and for grouping / filtering orders)
Net payment terms (in days). Used for invoice due dates.
Invoice comment
OBSOLETE: Use ProjectIds instead. Project ID - used if order is part of a project
(OBSOLETE: Use property on OrderForm instead) Order total without shipment cost
(OBSOLETE: Use property on OrderForm instead) Order total without shipment cost and without tax
(OBSOLETE: Use property on OrderForm instead) Total tax amount
(OBSOLETE: Use property on OrderForm instead) Order total, including shipment cost, tax, and discounts
(OBSOLETE: Use property on OrderForm instead) Order total, including shipment cost and discounts, but without tax
(OBSOLETE: Use property on OrderForm instead) Total order discount
Indicates whether the customer is new. Set automatically by the workflow if the customer's creation date is in the past, but can also be updated via the API.
Read only: Current version ID
Order name
Canceled date
Organization number
Correlation ID for tracing
Whether the order has been anonymized
Whether the order is reservable
List of invoice IDs associated with this order
Shows which documents have been generated for the order
Customer's own order number
Whether the order has been reallocated
Response
Success
True if workflow failed and is aborted
Changes
No recorded changes to this operation across all 1 revision of this API.