All notable changes to the API.

draft

• Add events to draft. A event will be added to the draft events list when the draft is updated.
• Add payout option to enable calculating the payout for the order items. See Billing API
• Add order_id option to allow creating a draft that will be added to an existing order.
• Add split_draft option to allow one-to-many mapping between draft and order
• Add support for including store when creating a draft.
• Add support for adding draft items with reversed_reason property. Use the property in case when an item should be reversed and the payment refunded.

order

• Include authorizations and cancellations in order details
• Support creating order directly without creating a draft
• Add payment_details to the order.

sessions Add support for creating sessions for and order

refunds Require items to be specified when creating a refund

captures Require items to be specified when creating a capture

cancellations Add support for creating cancellations for an order

authorizations Add support for creating authorizations for an order

orders Extend order definitions with Discounts

orders store orders add support for include_events on order requests. The order event state and events list will be included in the response.

• GET shopping/orders/
• GET shopping/orders/{order_id}
• GET shopping/customers/{customer_id}/orders/
• GET shopping/customers/{customer_id}/orders/{order_id}
• GET shopping/stores/{store_id}/orders/
• GET shopping/stores/{store_id}/orders/{order_id}

draft orders

• extend draft definition with optional options.serial_order_number_suffix property.

orders

• extend order definition with courier_id and pickup_at that can be set and updated after the order is created
• extend order definition with delivery_id that can be set after the the order is created
• extend order definition with optional pre_order property
• extend order definition with optional type property.
• extend order shipping_address and billing_address property with optional comment property that can be used for additional information needed for the address.

events

• allow scopes
  • read:shopping:/orders/ANY/events
  • write:shopping:/orders/ANY/events

draft orders

• filter by status: open, completed, deleted
• filter by created_at.gte and created_at.lte

customer orders

• filter by status: open, closed, cancelled
• filter by payment_status: pending, partially_paid, paid, partially_refunded, refunded
• filter by created_at.gte and created_at.lte

store orders

• filter by status: open, closed, cancelled
• filter by payment_status: pending, partially_paid, paid, partially_refunded, refunded
• filter by created_at.gte and created_at.lte

orders

• filter by status: open, closed, cancelled
• filter by payment_status: pending, partially_paid, paid, partially_refunded, refunded
• filter by created_at.gte and created_at.lte
• accept any customer.id format

order payments

• require amount and processed_at when creating a refund
• require amount and processed_at when creating a capture

store orders

• Add endpoint for list orders for a store
• Add endpoint for get order for a store

customer orders

• Remove uuid format requirement on customer_id path parameter

complete draft order

• remove support for apply_discounts query parameter, the parameter will only be supported from endpoints updating the draft order.

complete draft order

• change the response to include one or more orders created from the draft.

Rename the API, Shopping API, all endpoints will now be prefixed with

• /v1/accounts/{aid}/shopping/

order

• Add salesperson_id and salesperson_name properties
• Add delivery_at property for specifying when the order should be delivered (in the future)

order item

• Require percentage in tax_lines for an order item
• Add quantity property to item.additions, and allow negative gross_amount
• Add related_item property that can be used to create a relationship between two items
• Add description_alias, shorter item description for receipt
• Add salesperson_id and salesperson_name property

order item

• Add metadata property that can be used to included additional key/values on order items.
• Add additions array property. The property can be used to describe customization the customer want to be included with the order item.
• Add comment property for recording customer comments on the item

order

• Add comment property for recording customer comments on the order

Use webhooks to get notification on shopping events. See Create new subscription for details on how to create a webhooks subscription

Following event types are supported